-
Notifications
You must be signed in to change notification settings - Fork 1
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
No populate on request by default #26
Comments
Another question is maybe we should in get_data request store this populate. So we have two types of requests:
We don't use populate in collection (but we might), but we can just add populate to parameters and it works. But here we must duplicate this in the config (populate for collection, populate for resource) and it might be confusing. This is an open question to discuss how we should treat populate parameter. |
Related PR: #27 |
I think giving option to populate or not is a good idea, also it is good idea to keep the defaults on bare minimum. I will look into it, tests and will provide more feedback. Potentially can be included into next release. |
I think about parametrs for a collection and a resource but this might be overwhelming. In that case populate goes to parameters. |
@mkrajewski90 does your PR resolve this issue fully? |
@bluszcz - I have an issue here to resolve (I send it in my next PR) but I back to this PR I think we should no populate by default. I see some proper reasons not to do it:
My solution
Instead of
we can have
with populate method:
Please let me know what do you think about this.
The text was updated successfully, but these errors were encountered: