Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove ParseErrors::errors_as_strings (fix #543) #882

Merged
merged 2 commits into from
May 17, 2024

Conversation

john-h-kastner-aws
Copy link
Contributor

@john-h-kastner-aws john-h-kastner-aws commented May 17, 2024

Description of changes

There were three callers of this function in the wasm crate, but this function is simple enough that in lining it is not a problem. Possibly those calls should be updated to use rich information from miette. The callers might also be removed as part of #854.

Issue #, if available

#543

Checklist for requesting a review

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

  • A breaking change requiring a major version bump to cedar-policy (e.g., changes to the signature of an existing API).

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

  • Updates the "Unreleased" section of the CHANGELOG with a description of my change (required for major/minor version bumps).

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.

Signed-off-by: John Kastner <jkastner@amazon.com>
@john-h-kastner-aws john-h-kastner-aws added the breaking-change This is (likely) a breaking change label May 17, 2024
@john-h-kastner-aws john-h-kastner-aws changed the title Remove ParseErrors::errors_as_strings (fix #534) Remove ParseErrors::errors_as_strings (fix #543) May 17, 2024
@john-h-kastner-aws john-h-kastner-aws linked an issue May 17, 2024 that may be closed by this pull request
2 tasks
Copy link
Contributor

@cdisselkoen cdisselkoen left a comment

Choose a reason for hiding this comment

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

This looks good to me, although I do think the Wasm functions should use the detailed errors in the same manner as #800, but it's acceptable to defer that to #854.

@john-h-kastner-aws john-h-kastner-aws merged commit e48dd9a into main May 17, 2024
17 checks passed
@john-h-kastner-aws john-h-kastner-aws mentioned this pull request May 17, 2024
2 tasks
@john-h-kastner-aws john-h-kastner-aws deleted the remove_errors_as_strings branch May 21, 2024 23:15
@khieta khieta mentioned this pull request Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change This is (likely) a breaking change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove ParseErrors::errors_as_strings
3 participants