We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Most of these are about adding request mappings and permanent redirections.
URLs in Gemma Web should reflect a better terminology: datasets, platforms, elements, result sets, etc. as we use in Gemma REST.
This makes it easier to navigate as one can simply paste a suitable ID in the address bar.
A few patterns I'm thinking about:
Where identifiers can be any suitable ID.
Previous URLs should be converted into permanent redirections and organized in some kind of legacy controller.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Most of these are about adding request mappings and permanent redirections.
URLs in Gemma Web should reflect a better terminology: datasets, platforms, elements, result sets, etc. as we use in Gemma REST.
This makes it easier to navigate as one can simply paste a suitable ID in the address bar.
A few patterns I'm thinking about:
Where identifiers can be any suitable ID.
Previous URLs should be converted into permanent redirections and organized in some kind of legacy controller.
The text was updated successfully, but these errors were encountered: