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
Is your feature request related to a problem? Please describe.
When loading the children of a parent model, it would useful to enable sorting (and perhaps other modifications of the query) so that the response order is correct "out of the box".
Using the Star/Planet example from Vapor docs - we may want to sort planets in a Star by distance from the star:
Star.query(on: req.db).with(\.$planets)
...however this will not sort by our desired parameter, but by whatever default order the db engine returns.
A bit of complication/ugliness with the proposed API is that we also need the option to specify ASC or DESC. So, it would need to look like so (or something similar...maybe tuple, maybe enum w/ associated val):
Ultimately I don't think this is the right approach because it could allow filtering, paginating, etc. all of which would change the result in very unexpected ways.
Additional context
None.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
When loading the children of a parent model, it would useful to enable sorting (and perhaps other modifications of the query) so that the response order is correct "out of the box".
Using the Star/Planet example from Vapor docs - we may want to sort planets in a Star by distance from the star:
...however this will not sort by our desired parameter, but by whatever default order the db engine returns.
Describe the solution you'd like
An obvious candidate would be the
with()
method:Additionally it could take an array to provide multiple sorting options (though I suppose in the case of planets and stars this makes little sense:
A bit of complication/ugliness with the proposed API is that we also need the option to specify ASC or DESC. So, it would need to look like so (or something similar...maybe tuple, maybe enum w/ associated val):
Describe alternatives you've considered
Also thought about giving full control over the relationship query. So, something like:
Ultimately I don't think this is the right approach because it could allow filtering, paginating, etc. all of which would change the result in very unexpected ways.
Additional context
None.
The text was updated successfully, but these errors were encountered: