Finding impacted paths for query results with respect to actions #7

There's a lot to be considered if selecting a single query language for overlays, which is a given.

Looking at existing, supporting libraries for a selected query language is certainly one of those items to be considered.

In doing so, from an implementor's perspective, actions are potentially problematic if the existing libraries:

• Return immutable query results
• Are unable to provide the paths associated with query results

Some options:

1. Use a query language with explicit path-finding syntax. The query, itself, in this case, would return paths for the action. Example:

   jq 'paths(.paths."/v1/account".get.responses[] | select(.description == "Error response."))'
   

2. Use a query language with supporting libraries that either return mutable query results or associated paths.

The first option listed above has benefits in being an explicit intention by the author. I do have concerns about the second approach. There may be some edge cases where returning paths from query results may not be possible.

Something to consider.