Respect hash_access setting when using expose_nil: false option
#359
Conversation
This file contains 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
magni-
force-pushed
the
pp/358-expose_nil-hash_access
branch
from
dca7c1c
to
23043a3
Compare
|
@LeFnord Can you please approve the CI workflow? 🙏🏼 Tests pass locally |
|
Thank you @magni- |
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.
Fixes #358
The first commit is unrelated.
bundle exec rakesurfaced a Rubocop warning, so I figured I'd fix it.Grape::Entity.hash_access=was added back in #319, but I didn't realize it was a thing until I dove into the code, so I added it to theREADME.