Darío Cutillas

The PR is in draft until it is tested against a real repo.

The rationale between the chosen name for the manager, or better said the configuration option is that `jsonata` is to this manager what `regex` is to the Regex manager. >...

Yes, I agree to your observation of the the `type` naming. I just couldn't come up with a better name to indicate that we'll need to discriminate the type of...

I've now tested this PR against a real repository: https://github.com/dariocc/renovate-test. You can see the [generated PR](https://github.com/dariocc/renovate-test).

> I don't think we need to completely the unification with regex manager in this PR, or handle any migrating. So is it fine to merge this PR as it...

> Does your approach support "nested" queries, e.g. you can search inside multiple levels? Nested queries in the sense applied by regexManager aren't necessary if you have a document-aware language...

> please search existing issues, I'm pretty sure this is a duplicate. Could you suggest a query to find such duplicate? When I tried before creating this issue I wasn't...

I don't fully understand the relation of _being able to write functions_ to _being able to load code from external files_ however I do understand you want to be certain...

Let me know if you'd be interested in me creating a PR with an example of how a generic JSON manager could look like. And thanks in any case for...

> The question is whether it opens up too much of an attack surface, intentionally or not Yes that is understandable. > i think a alternative is jsonpath, which is...