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
Copy of BoxLang AI 3.4 Blog Series Part 5 : Reasoning Without the Guesswork
Reasoning-capable models have been usable in BoxLang AI for a while. params passes straight through to the provider body, so params: { thinking: { type: "enabled", budget_tokens: 10000 } } for Claude, or params: { reasoning_effort: "high" } for OpenAI, already reached the API. What never worked was reading the reasoning back. It was parsed out on arrival and silently dropped. In 3.4.0, that's fixed, and it's fixed the same way for every provider.
TestBox 7.1 Released : 47 New Ways to Assert, 29 of Them BoxLang-Only
TestBox 7.1.0 is here, and it is the largest single expansion of our assertion and expectation library since TestBox was born.
BoxLang 1.17 Series Part 4 : WriteDump Enhanced!
You call writeDump() on an ORM entity or a very rich class graph . The browser locks up. Thirty seconds later you get a page with forty thousand rows on it, you scroll for a while, you give up, and you go edit your code to dump a sub-key instead. Or worse, you crash the server.
Add Your Comment