Shaady Dawood

It is not ...widgetConfiguration.'['OButton']'.name But ...widgetConfiguration['OButton'].name With no dot before the brackets

This is by design Use '$["key-with-dashes"] not "$." For recursive query use '$..["key with spaces"]'

The syntax parser doesn't like invalid-indentifier names as keys in plain form For key names that are invalid identifier name you have to handle in two ways. - you can't...

It does support that, just the parser won't allow spaces "$[a,b]" with no spaces should work

The no-spaces is a parser Grammer limitation that can be easily fixed in the future. The behavior of the AST evaluation code (the handler function) is responsible for the data...

I'd say jsonpath should focus on query, safely and as fast as possible. Check out 'json-tots' on npm for transformations capabilities. Disclaimer: This is my own view, I'm not speaking...

See, our discussion and comparing problem scopes, one-query -> jsonpath language is specified. custom systematic transformation -> is where I started experimenting with json-tots, and focus on trasducer-pipelines for values...

I agree with Robert. Check 'json-tots' npm package for JSON document level operations and JSON transformation