You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This may be as well an issue in metastore-lib but I'm not sure if this is something we need to adress on the UX level or in the backend. When editing a Version the order in which they are displayed changes making it confusing to know which version is the first and which one is the last.
Steps to Reproduce:
Create a dataset and add a few versions.
Edit the name of one of the Versions (second version in this example) and save it
The versions are no longer shown in the same order
As far as I tested, this is not happening when using a github backend. Even so, it would be nice to the behaviour of both backends to be the same.
The text was updated successfully, but these errors were encountered:
As an aside can we consistently use RevisionTag (or Release if you want a nicer word) at least internally (i saw title and was not sure what this was about).
This should be reported in metastore-lib, in any case good catch. We need to find the expected behavior of tag_list - is it sort by creation time or alphabetically, and if creation time should it be newest first or oldest.
This may be as well an issue in
metastore-lib
but I'm not sure if this is something we need to adress on the UX level or in the backend. When editing a Version the order in which they are displayed changes making it confusing to know which version is the first and which one is the last.Steps to Reproduce:
As far as I tested, this is not happening when using a
github
backend. Even so, it would be nice to the behaviour of both backends to be the same.The text was updated successfully, but these errors were encountered: