Imprecise error messages of has
operations
#1329
Labels
internal-improvement
Refactoring, minor performance improvement, or other changes that Cedar users may never notice
papercut
Small annoyances in the Cedar SDK. Lower priority fixes than bugs. Smaller than a fature request
Describe the improvement you'd like to request
Consider the following ill-formed policy,
The CLI reports a parsing error as follows,
The error span should ideally only cover
if
, as opposed to the entirehas
expression.Describe alternatives you've considered
No response
Additional context
No response
Is this something that you'd be interested in working on?
The text was updated successfully, but these errors were encountered: