UI datasets ordering starting from 0 #2106
Merged
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.
Currently in the UI the datasets ordering is starting from 1, whereas the ordering in the backend start from 0.
This could create some confusion, when both conventions are reported in the UI, e.g., #2093.
Moreover, all the urls that contain some datasets identifiers use the backend convention (starting from 0).
My proposal is to unify the convention and make use of the 0ed one, this would also simplify its management in the UI.
Changes proposed
Check List (Check all the applicable boxes)