-
Notifications
You must be signed in to change notification settings - Fork 181
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
File and folder rename won't allow to change case #575
Comments
Hi. Thanks for the detailed feedback. We are currently reworking on the DB storage layers and many things will change in the deep layers of the server for the v5. In the meantime, I also have to go through the same process each time I make a "case" typo: I know the pain :) |
Thanks @bsinou for the info! I'll do that meanwhile... And now that you said that, I just noticed something: I haven't tried doing it using any of the APIs. Is this just a frontend check? Does it fail if I do it via API? So, to refresh it for both of us I just tested it: Cells APITo rename I do the same operation that the frontend does, a {
"nodes": [
"alvaro/testing"
],
"target": "alvaro/Testing",
"targetParent": false
} Result: It answers with a proper job WebDAV APIUsing the Cyberduck client, I try to rename S3 APICouldn't make it work, but I think it's either a problem with my client configuration or a limitation of the S3 API. I haven't had time to check it slowly... 🤷 Seems like the WebDAV API at least allows it. I have some WebDAV clients going around, so I hope there aren't any surprises waiting for me in the server if people begin to rename files using WebDAV 😆 |
Problem
If I want to change case for one or several letter of one of my files or folders ( e.g, I want to rename from
test-Alvaro
totest-alvaro
) it won't allow me as if the two file names were the same:From what I've seen, this is due to one of the React prompt validators switching everything to lower case before comparing the strings:
cells/frontend/front-srv/assets/gui.ajax/res/js/ui/ReactUI/modal/PromptValidators.js
Lines 29 to 35 in 0acafc8
This shouldn't be a problem as we're:
This looks like just a frontend check that maybe has a technical reason, or maybe not. Does it?
Meanwhile I'm changing the file name to an intermediate one (e.g.
test-Alvaro --> test-something --> test-alvaro
) and that works, but it's a bit of a hassle, so I'd like to know...Setup
Question
Does it make sense to:
The text was updated successfully, but these errors were encountered: