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
The dotenv library on npm, a popular node.js implementation, doesn't require escaping quotes inside quotes or support the use of \t, per motdotla/dotenv#711. It does support \n, though.
This results in inconsistency between the extension and resulting parsed strings, with newlines being correct, while tabs, escaped backslashes, and quotes inside quotes aren't:
On the issue linked above, they describe 3 other libs behavior, and they're also all inconsistent in some way with this extension.
So would extension settings to customize which escape sequences are counted be possible, or adequately deal with this? Is there a specification somewhere that these libs should be following?
(I do believe the extension's default styling is correct, for what it's worth, and that dotenv should support these things. I'm also aware that this extension is for a different lib.)
The text was updated successfully, but these errors were encountered:
The dotenv library on npm, a popular node.js implementation, doesn't require escaping quotes inside quotes or support the use of
\t
, per motdotla/dotenv#711. It does support\n
, though.This results in inconsistency between the extension and resulting parsed strings, with newlines being correct, while tabs, escaped backslashes, and quotes inside quotes aren't:
On the issue linked above, they describe 3 other libs behavior, and they're also all inconsistent in some way with this extension.
So would extension settings to customize which escape sequences are counted be possible, or adequately deal with this? Is there a specification somewhere that these libs should be following?
(I do believe the extension's default styling is correct, for what it's worth, and that dotenv should support these things. I'm also aware that this extension is for a different lib.)
The text was updated successfully, but these errors were encountered: