-
Notifications
You must be signed in to change notification settings - Fork 90
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
More tasks from #745 #1036
More tasks from #745 #1036
Conversation
Signed-off-by: Aaron Eline <aeline+github@amazon.com>
Signed-off-by: Aaron Eline <aeline+github@amazon.com>
Signed-off-by: Aaron Eline <aeline+github@amazon.com>
Signed-off-by: Aaron Eline <aeline+github@amazon.com>
Signed-off-by: Aaron Eline <aeline+github@amazon.com>
/// Creates a duplicate keys error | ||
pub fn duplicate_keys(key: SmolStr, loc1: Loc, loc2: Loc) -> Self { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since this type is publicly exposed, end-users can see and use these constructors, and we have to commit to stability for their arguments. I think it would be better if we could avoid (at least fully pub
) constructors, so that in the future we could add or change arguments as necessary?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed. I think our error constructors are generally not public
/// Creates a duplicate keys error | ||
pub fn duplicate_keys(key: SmolStr, loc1: Loc, loc2: Loc) -> Self { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
agreed. I think our error constructors are generally not public
Superseded by #1129 |
Description of changes
Cleans up two remaining error tasks
EntityUid::from_json
returns a concrete type instead of an existentialHumanSchemaError::Parse
is more transparentIssue #, if available
#745
Checklist for requesting a review
The change in this PR is (choose one, and delete the other options):
cedar-policy
(e.g., addition of a new API).I confirm that this PR (choose one, and delete the other options):
I confirm that
cedar-spec
(choose one, and delete the other options):