Skip to content

Conversation

@aaronjeline
Copy link
Contributor

Description of changes

Using reserved keywords as ids could cause the parser to panic instead of failing gracefully

Issue #, if available

N/A

Checklist for requesting a review

The change in this PR is (choose one, and delete the other options):

  • A bug fix or other functionality change requiring a patch to cedar-policy.

I confirm that this PR (choose one, and delete the other options):

  • Does not update the CHANGELOG because my change does not significantly impact released code.

I confirm that cedar-spec (choose one, and delete the other options):

  • Does not require updates because my change does not impact the Cedar formal model or DRT infrastructure.

Disclaimer

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Signed-off-by: Aaron Eline <aeline@amazon.com>
Signed-off-by: Aaron Eline <aeline+github@amazon.com>
Comment on lines 17 to 18
#[error("Invalid escape codes")]
StringEscape(NonEmpty<UnescapeError>),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not introduced by this PR, but it seems like it would be useful to print the UnescapeError content.

@aaronjeline
Copy link
Contributor Author

Closed at my git history got messed up, resubmitting in a second

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants