You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the tokenizer considers the entire contents of text between the open bracket and closed bracket the "key", including any whitespace that may be surrounding the actual text.
This is inconsistent with other formatters and the formatter built into the C# compiler.
Eg: abc{ Replacement1 } outputs the key " Replacement1 ", when it should really be "Replacement1".
Additionally, spaces are currently allowed in the middle of keys, which throws an "Unexpected Token" error in the C# compiler's string interpolation.
Both of these behaviours should eventually be configurable with a user specified setting value.
Currently the tokenizer considers the entire contents of text between the open bracket and closed bracket the "key", including any whitespace that may be surrounding the actual text.
This is inconsistent with other formatters and the formatter built into the C# compiler.
Eg:
abc{ Replacement1 }
outputs the key " Replacement1 ", when it should really be "Replacement1".Additionally, spaces are currently allowed in the middle of keys, which throws an "Unexpected Token" error in the C# compiler's string interpolation.
Both of these behaviours should eventually be configurable with a user specified setting value.
Items:
Trim(ReadOnlySpan<Char>)
The text was updated successfully, but these errors were encountered: