Add disallowed_attributes to StrongParametersSupport#842
Open
mswiszcz wants to merge 1 commit into
Open
Conversation
coorasse
approved these changes
May 23, 2024
Member
coorasse
left a comment
There was a problem hiding this comment.
I like this, but I'd like to have some tests for this feature. Thanks. ❤️
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hello!
We are using can_can_can with graphql-ruby on our project and recently I've been looking for an option to go through all incoming arguments (InputObject arguments) and allow only those which specific user can send.
When I tried to use permitted_attributes I've stumbled upon a problem with associations as our input object allows to send attributes which are not explicity attributes of a class.
Here's an example that describes it:
We could obviously expliclity mention that someone
can :update, Product, :titlebut that means whenever we add a translation to a new field, or an association and we miss updating ability.rb it will not allow updating it.