NOTES
1) Not sure if these characters are allowed in Mac filenames either. Also avoiding '>' probably a good idea even in linux systems since it could cause some problems with shell commands.
2) Would also need some trigger or check on commits to prevent new files being introduced with these characters: \, /, :, *, ?, ", <, >, |
3) I realize that WSL is recommended for development in a Windows environment, but this may be an easy fix to enable that scenario without WSL. However, not sure if these filenames are explicitly referenced in a database for e2etests, or how they are pulled. Aliasing or escaping may be necessary to ensure existing references still work.
REPRO:
EXPECTED:
NOTES 1) Not sure if these characters are allowed in Mac filenames either. Also avoiding '>' probably a good idea even in linux systems since it could cause some problems with shell commands.
2) Would also need some trigger or check on commits to prevent new files being introduced with these characters: \, /, :, *, ?, ", <, >, |
3) I realize that WSL is recommended for development in a Windows environment, but this may be an easy fix to enable that scenario without WSL. However, not sure if these filenames are explicitly referenced in a database for e2etests, or how they are pulled. Aliasing or escaping may be necessary to ensure existing references still work.