-
Notifications
You must be signed in to change notification settings - Fork 492
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
6873 shapefiles zip folders #7279
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. I'm very happy to see a test has been added to test the functionality. I'm also glad to see the whitespace cleaned up. WorldMapTokenTest.testTokenValues failed in the Jenkins run but that test fails for no reason from time to time.
…tomatically to the test class (#6873).
I often hesitate to fix existing formatting, because it "inflates" the diff and makes it harder to see the actual functional changes in the commit... But there were so many random extra tabs in that method - in some, but not all lines - that it was hard to view in Netbeans. |
@landreev yeah, what I'd rather see eventually is some sort of enforcement of a house style but for now with whitespace changes come in I make use of this button in GitHub to hide them while reviewing: |
What this PR does / why we need it:
Preserves folders found in shape file zip archives.
Which issue(s) this PR closes:
Closes #6873
Special notes for your reviewer:
The changes to FileUtil.java are mostly tabs and whitespaces - the formatting of the method I had to change was seriously off, I couldn't resist fixing it; actual code changes are relatively small there.
Suggestions on how to test this:
There's a test file provided in the issue: https://github.com/IQSS/dataverse/files/4588466/files.zip . It has 4 files constituting a shape set, plus 2 extra files. All files are in subfolders, that would be dropped by the application as it is now, but should be preserved by the code in the PR.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation: