Our template would always contain the variable value. However, as the code is currently you'd always end up with an exception. "The variable "x" can't be processed. Most likely a nested structure that is referenced is not a dictionary or the variable identifier was entered incorrectly"
This was undesirable because templates needed to stay fixed, contain the templated path, but not error out. ThrowIfNotFound was unhelpful because everything was being caught be the first if statement.
With this modification ThrowIfNotFound now works as expected.
We have many complex templates. One thing that we were struggling with was that our json objects sometimes have null properties.
The schema might look like this...
Or, like this...
Our template would always contain the variable value. However, as the code is currently you'd always end up with an exception. "The variable "x" can't be processed. Most likely a nested structure that is referenced is not a dictionary or the variable identifier was entered incorrectly"
This was undesirable because templates needed to stay fixed, contain the templated path, but not error out. ThrowIfNotFound was unhelpful because everything was being caught be the first if statement.
With this modification ThrowIfNotFound now works as expected.