One of my favorite updates to 2.6.0 is the ability to create complex elements on my settings using JSON notation. In previous versions, you had a very limited JSON notation, but now you have the full fledged notation. This is particularly useful if you want to override settings using the environment interceptor. You can actually override datasource elements or any part of the configuration file. It becomes tricky when overriding structures, but the notation helps out incredibly. Let's say that I have a datasource declaration like this on my coldbox configuration file:
But I would like to override or maybe add another datasource element. If I want to override then I can create a setting element on my environment file that can look like this:
This will override the datasources structure with the JSON inflated structure. This is really helpful when overriding complex variables and also for setting up new complex settings.
Blog
Recent Entries
MatchBox and WebAssembly: Running BoxLang in the Browser and at the Edge
The MatchBox open beta is live at https://boxlang.ortusbooks.com/boxlang-framework/matchbox, and it brings something genuinely new to the BoxLang ecosystem: a path into WebAssembly.
That means BoxLang code can now move into browser applications, static-site deployments, edge runtimes, and WASI-style containers - without requiring a JVM. The feature is still beta, but the core direction is already useful: write BoxLang, compile it with MatchBox, and ship the generated WASM artifact to wherever a small portable runtime makes sense.
One Language, Every Runtime: BoxLang Expands Beyond the Server
Discover how BoxLang’s multi-runtime architecture helps developers build beyond the server with support for serverless functions, desktop applications, CI/CD workflows, Java integrations, containers, runtime management, and more.
BoxLang 1.14.0 : Introducing Inner Classes
BoxLang has always embraced a simple truth: the way you organize code shapes the way you think about problems. For a long time, if you needed a helper class, you needed a file. One class, one .bx file, no exceptions. That's clean and predictable, but it creates real friction when a class is tightly coupled to exactly one caller and has no business existing anywhere else.
Add Your Comment