File names in extension can no longer contain spaces?
See original GitHub issueIt didn’t use to be a problem when packaging extensions, but since 0.3.40 I’m getting the error below:
error: Part Name 'vsts-snyk/node_modules/snyk/Contributor Agreement.md' is invalid. Please check the following:
error: 1. No whitespace or any of these characters: #^[]<>?
error: 2. Cannot end with a period.
error: 3. No percent-encoded / or \ characters. Additionally, % must be followed by two hex characters.
tfx failed with error: Error: C:\TFS\_W\3\s\node_modules\.bin\tfx.cmd failed with return code: 4294967295
Since I cannot enforce this kind of restriction on developers of 3rd party dependencies, it’s a very inconvenient change.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:7
Top Results From Across the Web
Can Spaces Exist Within A File Extension? - Stack Overflow
The extension on a filename in Windows is purely a convention. The GetExtension and HasExtension methods only look for a dot in the...
Read more >Why shouldn't spaces be used in filenames on the computer?
There is no legitimate reason to avoid spaces. All modern file systems handle file names with spaces just fine. Some folks say you...
Read more >Problems with filenames and links - University of St Andrews
Whether or not the spaces are replaced with underlines, links to files that have spaces in their names will fail on the Web...
Read more >ACCESSIBLE FILE NAMES: Please...No Spaces and/or ...
ACCESSIBLE FILE NAMES: Please…No Spaces and/or Special Characters · Don't start or end your filename with a space, period, hyphen, or underline.
Read more >Characters to Avoid in Filenames and Directories
Illegal Filename Characters · Don't start or end your filename with a space, period, hyphen, or underline. · Keep your filenames to a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Issue still open?
To get around this problem we have been running an in-line Powershell script prior to running the VSIX packaging step.
The code is as follows