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 Brings BoxLang to ESP32 Microcontrollers 🦀
One of the most unusual parts of MatchBox is the ESP32 target.
The MatchBox open beta is available at https://github.com/ortus-boxlang/matchbox, and it can compile BoxLang scripts into bytecode and deploy them to ESP32 microcontrollers. That means the same language used for scripts, native tools, web services, and browser logic can also run on a small embedded device.
BoxLang AWS, Azure, and Google Secrets Manager Module Released
Every production application carries secrets: database passwords, API tokens, encryption keys. The question is never whether to manage them -- it's how badly the current approach is going to hurt you.
BoxLang 1.14.0 : BoxLang Ranges Part 2: Teach BoxLang Your Types with `IRangeable`
In Part 1, we covered BoxLang's first-class range system: lazy evaluation, exclusive boundaries, built-in types (integers, decimals, characters, dates), custom stepping, Java Stream integration, and contains() semantics. If you haven't read it yet, start there.
Add Your Comment