You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to have an option to set the limit of populated items - as there can be thousands of them and it's not very useful to have such a huge response...
If we can also support a skip parameter - that would be just perfect.
I see you have removed the limit option, can we put it back?
The text was updated successfully, but these errors were encountered:
art1c0
changed the title
Support for skip/limit
Support for skip & limit
Oct 6, 2017
This option was removed as I wasn't sure of a use case where this would be useful?
If there are a bunch of associated records, I wasn't sure what value there would be populating some of them, because it would effectively be random which ones you get?
Unfortunately I've lost access to this repo though, so am not able to make further changes, see #8
Thank you for the explanation!
In fact this option would be quite useful, especially together with "skip", as it even allows to make pagination of populated objects... Or at least it would be possible to get some "last 10" elements using "sort" parameter.
It would be nice to have an option to set the limit of populated items - as there can be thousands of them and it's not very useful to have such a huge response...
If we can also support a skip parameter - that would be just perfect.
I see you have removed the limit option, can we put it back?
The text was updated successfully, but these errors were encountered: