Simplified try-catch strategy in DataWeave with the default keyword (instead of try/orElse)
The other day I was reading some StackOverflow DataWeave questions (as one does) and I got to this very interesting thread: Why the “default” keyword acts like “try + catch / orElse” in some cases. I wanted to take a moment to create an article about my own explanation of what I see in that thread.
Check out this article I wrote on ProstDev 👇