BUGFIX: Disallow all whitespace in filenames #1147
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
d0sboots
reviewed
Mar 8, 2024
|
How do I bump the version? Just increment 38 to 39? Anything else I need to do? |
|
Ye, just increment |
Snarling
reviewed
Mar 8, 2024
LJNeon
force-pushed
the
fixWhitespaceInFilenames
branch
from
1350f04 to
7f6f259
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently only the space character " " invalidates a filename, all other whitespace characters are allowed. This PR expands the invalid character list to include all whitespace and corrects all filenames with whitespace in existing saves.
This has been tested by @Fireball5939.