Allow clients to specify GraphQL relationship order#3750
Merged
josephsnyder merged 1 commit intoMay 28, 2026
Conversation
All relationships currently have a hardcoded ordering by ID, with the direction chosen somewhat arbitrarily based on the expected page render order. This commit switches the default order for all filterable relationships to ID, ascending. This commit also adds the ability for clients to specify an `orderBy` input parameter which accepts a list of columns and their respective orders. For example: `orderBy: [{column: NAME, order: ASC}]`. This capability allows us to integrate client-side table sorting with the GraphQL queries used to fill those tables. Additionally, this feature will allow us to use GraphQL to query data for plots throughout the site.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
All relationships currently have a hardcoded ordering by ID, with the direction chosen somewhat arbitrarily based on the expected page render order. This commit switches the default order for all filterable relationships to ID, ascending. This commit also adds the ability for clients to specify an
orderByinput parameter which accepts a list of columns and their respective orders. For example:orderBy: [{column: NAME, order: ASC}]. This capability allows us to integrate client-side table sorting with the GraphQL queries used to fill those tables. Additionally, this feature will allow us to use GraphQL to query data for plots throughout the site.