Last active
December 14, 2015 11:59
-
-
Save zerowidth/5083123 to your computer and use it in GitHub Desktop.
output of toml-test run for toml-parslet library
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1.9.3-p385 macallan:~/Desktop/toml-test (master)? ▸ ./toml-test /Users/nathan/code/toml-parslet/script/toml-test.sh | |
Test: duplicate-keygroups (invalid) | |
Expected an error, but no error was reported. | |
------------------------------------------------------------------------------- | |
Test: duplicate-keys (invalid) | |
Expected an error, but no error was reported. | |
------------------------------------------------------------------------------- | |
Test: empty-implicit-keygroup (invalid) | |
Expected an error, but no error was reported. | |
------------------------------------------------------------------------------- | |
Test: key-no-whitespace (invalid) | |
Expected an error, but no error was reported. | |
------------------------------------------------------------------------------- | |
Test: array-empty (valid) | |
#<TOML::ParseError: unexpected input at line 1 column 1> | |
------------------------------------------------------------------------------- | |
Test: key-special-chars (valid) | |
#<TOML::ParseError: unexpected input at line 1 column 1> | |
------------------------------------------------------------------------------- | |
Test: string-escapes (valid) | |
Values for key 'backslash' don't match. Expected a value of 'This string has a \ backslash character.' but got 'This string has a \\ backslash character.'. | |
44 passed, 7 failed |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
duplicate-keygroups
The behavior for duplicate key groups isn't clearly defined, especially since there are no values defined within. Need clarification.
duplicate-keys
Will fix. (Not mentioned explicitly in the spec tho)
empty-implicit-keygroup
Will fix.
key-no-whitespace
Per the spec, keys are non-whitespace characters, and there doesn't have to be whitespace between a key and the
=
character.array-empty
Undefined in spec, will ask for clarification. Easy to fix tho.
key-special-chars
From the spec: "Keys start with the first non-whitespace character and end with the last non-whitespace character before the equals sign". This implies that keys cannot contain the
=
character.string-escapes
Will fix.