Closed techgaun closed 6 years ago
Thanks :)
Dogma.Util.ScriptStrings
needs to be re-written to be honest, there's a ton of edge cases it doesn't handle correctly.
SpaceAfterComma
could be smarter too. Checking the source directly isn't very robust.
Seems like the root cause is how
Dogma.Util.ScriptStrings
strips the string literal contents and it seems to affectSpaceAfterComma
. If there's a code with comment that contains single double-quote, it seems to create this issue.Below is the sample code-block that can produce this behavior: