-
-
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
[stable28] fix(files): Correctly validate new node name #47035
Conversation
7f3b516
to
c4ec230
Compare
c4ec230
to
50a404c
Compare
Restarted cypress, but failure looked suspiciously related |
Failure related |
@skjnldsv what is the next step here? |
Fixing the tests 🤭🤭 |
@skjnldsv sorry I don't fully get what you mean. The reason I ask is because this is for a support ticket that is meeting the SLA soon. Can this please be merged? Or can you give me a date when it can to be merged? Or otherwise tell me a next step concretely (who does what when) |
@DaphneMuller should be in next maintenance releases |
50a404c
to
27538b5
Compare
drone is unrelated |
* 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 <opensource@fthiessen.de>
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
27538b5
to
adbffd6
Compare
Backport of #46767
Warning, This backport's changes differ from the original and might be incomplete⚠️
Todo
Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.