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.
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
Ruby: Add
rb/weak-cookie-configurationquery #7313Ruby: Add
rb/weak-cookie-configurationquery #7313Changes from all commits
8a3d1fe737f7335ce6e63897646971c5711db967bd2cd02159821c4ad977e8a7f01be77d3932ddadaf2536ea360712972cda8c745File filter
Conversations
Jump to
There are no files selected for viewing
nickrolfeJan 5, 2022
Contributor
I noticed some results for this class are actually reads, not writes. For example: https://github.com/gitlabhq/gitlabhq/blob/6d29831123c8c806dc75d64e29b7691576cbea7f/lib/gitlab/database.rb#L187
It's a private class, and the way it gets used with specific setter method names means it should be ok, but I wonder if we should save ourselves some headaches for future uses, either by restricting the class more, or adding a note in a comment.
alexrfordJan 5, 2022
Author
Contributor
Definitely makes sense to restrict these classes further - I've restricted
Settingnodes to ones that correspond to aSetterMethodCall.