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

Schema parameter 'only' overrides other options #165

Closed
lustdante opened this Issue Mar 13, 2015 · 1 comment

Comments

Projects
None yet
2 participants
@lustdante
Contributor

lustdante commented Mar 13, 2015

Is this intended behavior?

I made RESTful API so that customer can make request with customize fields.

Despite setting exclude to hide sensitive properties, providing the field in only still allowed schema to dump the properties.

@sloria

This comment has been minimized.

Member

sloria commented Mar 16, 2015

Indeed, only takes precedence over exclude. You raise a valid point, though; the only parameter is typically used for filtering in HTTP APIs, and I don't see any reason exclude should not be respected.

Will look into this further.

@sloria sloria added this to the 2.0-a milestone Mar 16, 2015

@lustdante lustdante closed this Mar 23, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment