-
Notifications
You must be signed in to change notification settings - Fork 2
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
fix: case sensitive file extension checks and force them to lower cas… #201
Conversation
Coverage reportClick to see where and how coverage changed
This report was generated by python-coverage-comment-action |
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.
Could you write/adjsut an integration test that:
- uploads an example.TXT
- uploads an example.txt
- uploads an example.TXT.meta.json
and checks that only the example.TXT has the correct metadata ?
Are we considering lower and upper case to be different files then? I think that wouldn't be immediately obvious to me as a user. |
Hey @mathislucka
We probably need to. It depends on your file system how case sensitivity is treated. We can't enforce a casing on upload without running into the problem of overwriting data. |
We decided that we will not continue on this fix and document that customers files need to end with lower cased extensions. |
Could we add an explicit warning to the upload command? I'm afraid that users won't check the documentation. |
The warning could say: Make sure your files have lowercase extensions, for example, my_file.pdf, instead of my_file.PDF. The SDK doesn't upload files with uppercase extensions. |
…e on upload
Related Issues
Proposed Changes?
Force the file extension to be lower case to check against allowed extensions and on upload. All other checks, like checking for metadata files are left untouched.
How did you test it?
Adjusted unit tests.
Notes for the reviewer
Screenshots (optional)
Checklist