Cedar error messages and suggestions should be better for "common operator errors, such as AND instead of &&" (that was the example in feedback I got). We should think about what all keywords/symbols people might try to use as operators, and provide reasonable suggestions. Possibly-incomplete list:
and (case insensitive) -> &&
or (case insensitive) -> ||
& -> &&
| -> ||
? -> suggest if-then-else? (for people coming from languages with C/Java-style ternary)
other suggestions?
Describe alternatives you've considered
N/A
Additional context
No response
Is this something that you'd be interested in working on?
[ ] 👋 I may be able to implement this feature request
Is this something where we can create a framework for this style of error, and then we can solicit PRs from the community for the most useful/impactful replacements?
Category
Error message improvements
Describe the feature you'd like to request
Cedar error messages and suggestions should be better for "common operator errors, such as
AND
instead of&&
" (that was the example in feedback I got). We should think about what all keywords/symbols people might try to use as operators, and provide reasonable suggestions. Possibly-incomplete list:and
(case insensitive) ->&&
or
(case insensitive) ->||
&
->&&
|
->||
?
-> suggest if-then-else? (for people coming from languages with C/Java-style ternary)Describe alternatives you've considered
N/A
Additional context
No response
Is this something that you'd be interested in working on?