-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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(files): Correctly validate new node name #46767
Conversation
/backport to stable29 |
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.
Except for synonym addition, lgtm
triggerActionForFile('file.txt', 'rename') | ||
|
||
getRowForFile('file.txt') | ||
.findByRole('textbox', { name: 'Filename' }) |
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.
Fancy!
/compile rebase-amend / |
* Resolves #45409 This includes two fixes: 1. The name in the "new node" dialog is correctly selected (e.g. `file.txt` only `file` is selected by default), to allow quick naming 2. `@nextcloud/files` functions for filename validation are used, this allows to use new Nextcloud 30 capabilities (e.g. reserved names) Signed-off-by: Ferdinand Thiessen <[email protected]> Signed-off-by: nextcloud-command <[email protected]>
cfa878e
to
dd88fa0
Compare
Hi @susnux |
@Jerome-Herbinet yes please open a ticket :) |
Summary
This includes two fixes:
file.txt
onlyfile
is selected by default), to allow quick naming@nextcloud/files
functions for filename validation are used, this allows to use new Nextcloud 30 capabilities (e.g. reserved names)Screen recording
Bildschirmaufnahme_20240725_215605.webm
Checklist