-
Notifications
You must be signed in to change notification settings - Fork 494
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
3758 file page preview #6325
3758 file page preview #6325
Conversation
@pdurbin @sekmiller thanks for the feedback, I attempted to address it in a992e0e. If there are still questions let's talk in the morning, but if it looks all good feel free to send it on to QA. |
Moving over to QA, we talked about the docs in standup and everything is good there. |
So, found a couple issues that need decisions on:
|
One possible solution to keep this moving is to not show previews on older versions for now. (i.e. we should treat this in the context if the already known issue that older versions show download buttons when later version is restricted). |
I just talked briefly with @sekmiller and @scolapasta. I'm OK not showing previews on previous versions in order to deal with this issue for now as I'd like to get this out because it provides immense value. @sekmiller is going to make the change. |
Fix for only showing File Preview tab when you're on the latest version of the file is checked in and available for verification. |
current version change looks good but found one additional issue, that is I had seen it but just realized it was an issue:
|
OK. Actually, since we're using the same logic as the display of the public download URL, if the file is restricted you cannot see the preview even if you have access. |
@sekmiller @kcondon Thanks, this is how I expected it to work before editing the docs yesterday and it's acceptable to me. :) I'll revert those changes. |
Reverted in 29a7edc |
New Contributors
Welcome! New contributors should at least glance at CONTRIBUTING.md, especially the section on pull requests where we encourage you to reach out to other developers before you start coding. Also, please note that we measure code coverage and prefer you write unit tests. Pull requests can still be reviewed without tests or completion of the checklist outlined below. Note that we use the "closes" syntax below to trigger Github's automation to close the corresponding issue once the pull request is merged.
Thanks for your contribution to Dataverse!
Related Issues
Pull Request Checklist