-
Notifications
You must be signed in to change notification settings - Fork 16
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
321 default dataset version #442
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Just a question and some suggestions only.
src/dataset/infrastructure/repositories/DatasetJSDataverseRepository.ts
Outdated
Show resolved
Hide resolved
src/sections/shared/form/DatasetMetadataForm/useSubmitDataset.ts
Outdated
Show resolved
Hide resolved
Thanks @GermanSaracca I made the suggested changes - the component test is failing in the last run only because I had to re-run it, and the coveralls script failed the second time since the coverage report had been created on the first run. I'm not sure why the component tests had to be re-run, it seems like maybe a failure to get the stock images for the metadata test? |
What do you mean by stock images ? I couldn't find that part of the code, are we using an external images library in some test? Approving 🚀 , we can discuss about those test for another iteration I believe 👍🏼 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! All changes were resolved!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
What this PR does / why we need it:
Changes the default dataset version requested from :latest to :latest-published. This is needed to match the behavior of the JSF. In the JSF, If a dataset has a draft version and a published version, View Dataset page shows the published version by default (when there isn't a version search param in the url).
Which issue(s) this PR closes:
Closes #321
Special notes for your reviewer:
Now that the default version is :latest-published, in order to view the draft version of a dataset, you need to add 'version=DRAFT' to the view dataset url. (The draft version used to be displayed by default when the user has permission to view it).
Suggestions on how to test this:
Create a dataset that has a published version and a draft version. Test that the version displayed in the View Dataset page is the published version, when no version search param is used.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
no
Is there a release notes update needed for this change?:
Additional documentation: