-
Notifications
You must be signed in to change notification settings - Fork 22
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
Optional resource attribute enforcement #82
Optional resource attribute enforcement #82
Conversation
Please, point the PR towards the |
Hey @PeterBolha thanks for the contribution! Thus, instead of returning That way we'll not need the optional wrapper, and therefore a mechanism/switch to enable it. @c00kiemon5ter does this sound reasonable? |
Yes, it makes sense. This is what the RFC specifies
emphasis on MAY, meaning that requests without the |
4760e56
to
463def8
Compare
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.
Fixes will be needed on tests after this change.
I have fixed the related test, however there are two more failing ones. I've rebased my branch to have the latest |
Thanks! Don't worry about these tests. Let's wait a bit before we merge this, and if necessary I'll ask you to rebase your branch later on. |
26f4aa7
to
9cdf4ae
Compare
Fixes #81
Provides a wrapper method that does not return an error when the validate resource attribute policy is set but the attribute is not provided in the client's request.