Skip to content
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

Fixed exposure of attributes marked as safe when using hash models. #110

Merged
merged 1 commit into from
Mar 10, 2015

Conversation

croeck
Copy link
Contributor

@croeck croeck commented Mar 10, 2015

The valid_exposure check now also accepts Hash objects that have a key matching the attribute's name.
Fix includes spec that demonstrates the issue and fails without the changes.

…he valid_exposure check now also accepts Hash objects that have a key matching the attribute's name.
@croeck croeck force-pushed the safe-exposure-of-hash-objects branch from 5636996 to e4d3a2b Compare March 10, 2015 10:55
@dblock
Copy link
Member

dblock commented Mar 10, 2015

Thanks.

dblock added a commit that referenced this pull request Mar 10, 2015
Fixed exposure of attributes marked as safe when using hash models.
@dblock dblock merged commit c3a1acd into ruby-grape:master Mar 10, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants