Fix: file name breaking Windows file naming rules #362
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
aboedo
force-pushed
the
fix/file_names_break_windows_file_system
branch
from
6e33524
to
0ad9bd9
Compare
vegaro
approved these changes
Sep 30, 2020
Closed
aboedo
added a commit
that referenced
this pull request
Oct 1, 2020
* renamed file removing '<' and '>' since those characters break naming rules on windows. * renamed test file
Merged
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.
Renamed
ArraySlice<UInt8>+Extensions.swift->ArraySlice_UInt8+Extensions.swiftto fix issues on Windows.Addresses #361