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
In contrast, it should produce an error, per the spec:
All other escape sequences not listed above are reserved and, if used, TOML should produce an error.
Restoring this to an error would make this library's behavior consistent with toml-j0.4 and @iarna/toml.
Valid TOML with a slash in the key name would be either of these:
["the\\key"]
one = "one"two = 2three = false
or Edit: The one below seems to be an extension that's on the 1.0 track, but not in 0.4. It's currently supported, however.
['the\key']
one = "one"two = 2three = false
The text was updated successfully, but these errors were encountered:
iarna
changed the title
Backslashes may ONLY precede valid escapes, pre the spec.
toml-node allows escape sequences not defined in the TOML spec in double quoted strings
Jun 16, 2018
This appears to have been introduced by: #21
To sum up the problem:
Given the following TOML:
This library produces:
In contrast, it should produce an error, per the spec:
Restoring this to an error would make this library's behavior consistent with
toml-j0.4
and@iarna/toml
.Valid TOML with a slash in the key name would be either of these:
or Edit: The one below seems to be an extension that's on the 1.0 track, but not in 0.4. It's currently supported, however.
The text was updated successfully, but these errors were encountered: