Skip to content
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

Added sorting information to configuration parameter values #272

Conversation

ricardogsilva
Copy link

@ricardogsilva ricardogsilva commented Oct 11, 2024

This PR adds a sort_order property to configuration parameter values which can be modified in the admin.

This sort order is later used for building the parameter combinations that are useful for the frontend to build its menus, i.e. in the /api/v2/coverages/forecast-variable-combinations and /api/v2/coverages/historical-variable-combinations API endpoints.

This PR does not actually expose the sort order in the API endpoint that provides variable combinations, but rather already provides this output sorted correctly. This means that the frontend client would not need to worry about sorting the output of the API. Regardless, if needed, the sort_order property can be found in the api/v2/coverages/configuration-parameters API endpoint


Also sorted the combinations for forecast variables
Also sorted the combinations for historical variables
@ricardogsilva ricardogsilva marked this pull request as ready for review October 14, 2024 10:17
@francbartoli francbartoli merged commit f252653 into geobeyond:main Oct 14, 2024
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement a way to sort a configuration parameter's possible values manually
2 participants