Open YangLyu89 opened 6 years ago
We should be consistent about what type of slashes we use.
We also have an issue that the schema flags backslashes as errors, even though they are accepted by the tool.
All our tooling should be consistent, using forward slash.
But we should accept both slashes, and in all cases where we see a forward or back slash, we should interpret that as "path separator character for the current OS."
The schema should be updated to accept both, but Visual Studio should provide a warning when it sees backslashes informing the user that they won't work on other operating systems.
Minimal repro steps
Expected result
The libman.json should be look like something:
Actual result