This repository was archived by the owner on Jan 14, 2025. It is now read-only.
[ORCT-152] - ordering support on backend #170
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…; apply partialy QueryBuilder to services
Ehevi
approved these changes
Aug 16, 2023
Collaborator
Ehevi
left a comment
Ehevi
left a comment
There was a problem hiding this comment.
Looks good to me :)
And we're finally above the 50% coverage! ^^
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have a JIRA ticket
Notable changes for developers:
ORDER BYclause in sql). Syntax:/?order[FIELD_NAME]={ASC|DESC}. Phrase can be repeated many time. e.g./?order[runNumber]=ASC&order[timeO2Start]=DESC, what will result in sqlORDER BY run_number ASC, time_o2_start DESC. Remember that order of 'order' params in url searchParams matters.QueryBuilderfor sequelize related functionalities