-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Renaming Part issues (slash symbols should not trigger any issue) #14477
Comments
@RomanPudashkin There is also case sensitive issue with workspace name bandicam.2022-11-11.15-26-47-995.mp4 |
Using slash symbol (/) probably is most dangerous (see #19054) |
@RomanPudashkin I thought a fix for this was addressed here? #14290 But certainly it seems it is still possible to enter "excluded" characters in 4.1.1. |
See #16127 how slash symbols are dangerous |
@cbjeukendrup just confirming whether you are still pursuing a fix for this? |
Yes! This is one of the next things I'll do. |
Some algorithms were implemented in #14288 #14290.
The current issue collects all other problems.
THIS BEHAVIOR WAS CHANGED IN #20210 AND SPECIAL SYMBOL ARE ALLOWED IN PART NAMES BUT IT DOESN'T TRIGGER ANY ISSUE BECAUSE OF SAFE IMPLEMENTATION (THAT'S THE FIX)
bandicam.2022-11-11.15-07-10-999.mp4
[THIS IS FIXED in duplicated_parts_fix #18999] When renaming parts, the filter mechanism should not be case sensitive. I.e. it should not allow to create Violin and violin
This is important for Uncompressed MuseScore folder format
[THIS IS LOGGED SEPARATELY When renaming part, it should allow to create more than one SPACE in name. #20408 ] When renaming part, it should allow to create more than one SPACE in name
bandicam.2022-11-11.15-09-26-315.mp4
Platform information
macOS, Windows, Linux
Additional context
#16127 #14288 #14290
The text was updated successfully, but these errors were encountered: