You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When writing JSONPath expressions, it's common to make mistakes where the expression is syntactically valid but matches nothing. Currently bump overlay just silently ignores such targets, which complicates troubleshooting.
It would be nice if the tool could warn the user about such noop targets. These warnings could be either always on, or enabled by some flag. For example speakeasy overlay apply has the --strict flag for this purpose.
Later this endpoint gets renamed (e.g. /foos/{id} becomes /foos/{foo_id}) or its operationId gets changed (e.g. maybe op IDs are autogenerated and the algorithm changes).
As an overlay author and maintainer, I would like to get notified about non-matches so that I can update the overlay to match the current state of my API.
The text was updated successfully, but these errors were encountered:
When writing JSONPath expressions, it's common to make mistakes where the expression is syntactically valid but matches nothing. Currently
bump overlay
just silently ignores such targets, which complicates troubleshooting.It would be nice if the tool could warn the user about such noop targets. These warnings could be either always on, or enabled by some flag. For example
speakeasy overlay apply
has the--strict
flag for this purpose.Some common errors:
Typos in node names, values, filters:
Skipping nodes in a path:
Extra nodes in a path:
Consider an overlay that targets an endpoint by its path or
operationId
:Later this endpoint gets renamed (e.g.
/foos/{id}
becomes/foos/{foo_id}
) or itsoperationId
gets changed (e.g. maybe op IDs are autogenerated and the algorithm changes).As an overlay author and maintainer, I would like to get notified about non-matches so that I can update the overlay to match the current state of my API.
The text was updated successfully, but these errors were encountered: