-
Notifications
You must be signed in to change notification settings - Fork 4
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
bug(filterApi) Projection filter options being ignored #170
Comments
Also, weirdly, this seems to have changed the order of the resulting data :-/ |
This one is just ridiculously weird. The SQL is all fine, but when it's rendered the model instances are completely different. I do need to add tests to ensure fields not in the projection are properly included/excluded. I had a quick look, but I really have no idea just now. Note to self: make tests for more than just |
Added checks for filter endpoint returning unwanted attributes #170
I think I've figured this out. Using Suggested alternative is to control the rendering to json rather than trying to modify how rails does the query. Controlling the json rendering is more supported and easier to change. e.g. have another look at jbuilder (which is added by default with Rails 4) |
POST staging.ecosounds.org/audio_recordings/filter
with body of:
Returns data items like this (full entities):
This bug is currently is only on staging - it appears to be a regression not caught by tests.
The text was updated successfully, but these errors were encountered: