436fac6afa
This PR fixes the scheme resolution bug outlined in #5326 The approach is as follows: * In [SchemeManager.cs], find the first scheme parser that actually successfully parses the scheme, as opposed to the existing code, which finds the first scheme parser which _says it can parse the scheme_, as that logic spuriously returns `true` currently. * In [XmlSchemeParser.cs] and [JsonParser.cs], ensure that the contents of the file are read and the contents passed to XmlDocument.LoadXXX, as this fails with an UriException on WSL otherwise. * Remove `CanParse` as it is superfluous. The check for a valid scheme parser should not just check an extension but also if the file exists - this is best done by the `ParseScheme` function as it already returns null on failure. * Add `FileExtension` to the interface because we need it lifted now. Closes #5326 |
||
|---|---|---|
| .. | ||
| ConsoleTargets | ||
| Properties | ||
| SchemeParsers | ||
| SchemeWriters | ||
| App.config | ||
| ColorScheme.cs | ||
| ColorTable.cs | ||
| ColorTool.csproj | ||
| ConsoleAPI.cs | ||
| ConsoleAttributes.cs | ||
| Program.cs | ||
| Resources.Designer.cs | ||
| Resources.resx | ||
| SchemeManager.cs | ||