* Release KDL 2.0.0
* fix grammar for multiline quoted strings to allow escaped whitespace on closing line
* Add unicode-space to raw string
* Remove nonexistent equals-sign from the grammar (#435)
* fix multiline string tests
* grammar: fix disallowed-keyword-identifiers and string-character (#436)
* Back out "fix multiline string tests"
This backs out commit 0c5604b462.
* add extra javascript implementation (#437)
* reword interaction multiline + whitespace escape (#439)
* More tests for backslash behaviour (#438)
* More tests for baskslash behaviour
* Incorrect example of escaped final newline
* Test with non-literal indent
* Make line-space a superset of node-space (#440)
* Allow escline everywhere
* escline tests
* Always escape \ inside single quotes in the grammar text (#441)
to match the other uses of it and the metalanguage description below
* Add tests for mandatory whitespace between arguments or properties (#442)
* Add an optional version marker (#444)
* Add version marker to the grammer
* Add version marker to the Changelog
* Update SPEC.md
Co-authored-by: eilvelia <hi@eilvelia.cat>
* add a mandatory newline after the version marker
* add mandatory space between version number
---------
Co-authored-by: eilvelia <hi@eilvelia.cat>
* Fix a changelog line erroneously truncated in #444 (#445)
* fix: move vertical tab to the line-breaking whitespace to match Unicode (#446)
* add vertical tab change test
* final tweaks before release
---------
Co-authored-by: eilvelia <hi@eilvelia.cat>
Co-authored-by: Bram Gotink <bram@gotink.me>
Co-authored-by: Thomas Jollans <tjol@tjol.eu>
Co-authored-by: Evgeny <eugenesvk@users.noreply.github.com>
* Make the raw-string productions non-greedy, and describe the infallibility. Closes#415
* More explicitly use and reference a cut point, rather than infallibility.
* Indicate expected-fail tests with a _fail suffix. Fixes#365
* Update the README with directions for formatting failing tests
* Add a lint for failing and orphaned tests.
These rules are a bit more liberal than what was described previously,
but I think they're clearer and more consistent:
* This way, strings have the (I think intuitive) property that, when
you 'blindly' remove the whitespace escapes, the meaning is
unchanged.
* If you take any valid single-line string and add a newline character
and some indentation both at the start and the end, the string will
still be valid (and unchanged) - previously, this was not necessarily
the case if there were whitespace escapes.