Merge KDL v2 #286
Merge KDL v2 #286
Commits on Aug 28, 2022
-
-
KQL: remove map operator and accessors (#222)
Honestly, they're just too implementation-specific
-
Allow "empty" single line comments in the spec (#234)
As I read the grammar in the spec, `"//"` wouldn't parse as a single-line-comment as it requires as least one non-newline character after the slashes.
-
-
Commits on Sep 1, 2022
-
Add escaped whitespace to KDL strings (#290)
* Add escaped whitespace to KDL spec * Add test cases for escaped whitespace * Spelling error
-
Add escaped whitespace note to v2 changelog (#291)
* Add escaped whitespace note to v2 changelog * Make changelog note on escaping whitespace more detailed
Commits on Sep 2, 2022
Commits on Oct 9, 2022
-
Add draft grammar for KQL 1.0.0 (#303)
* Add draft grammar for KQL 1.0.0 * Change whitespace in KQL grammar * Update KQL grammar to use new operators
Commits on Oct 6, 2023
Commits on Dec 11, 2023
-
Update formal grammar for KDL 2.0 (#285)
Fixes: #284 * Update formal grammar * Update SPEC.md for KDL 2.0 preview * Update SPEC.md Co-authored-by: Christopher Durham <[email protected]> --------- Co-authored-by: Tab Atkins Jr <[email protected]> Co-authored-by: Kat Marchán <[email protected]>
3 people authoredDec 11, 2023
Commits on Dec 13, 2023
-
allow ,<> as identifier characters since they no longer need to be re… (
#352) * fix some confusion in grammar syntax, and actually specify the syntax itself Fixes: #345 * allow ,<> as identifier characters since they no longer need to be reserved * fix typo * disallow more code points and outright ban certain ones from KDL documents altogether (#353) Fixes: #250 * `r` prefix is no longer required for raw strings (#354) Fixes: #337
-
-
-
-
-
-
Clarify that multiline comments are allowed after line continuations,…
… per grammar Fixes: #322
-
-
-
-
-
-
Commits on Dec 17, 2023
Commits on Dec 26, 2023
-
Remove now-irrelevant comment about idents acting like strings (they …
…*are* strings now).
-
-
-
-
-
-
-
Tests are invalid (contained U+FFFD, not surrogates) and are in gener…
…al untestable since you can't represent surrogates in UTF-8, which KDL must be encoded in.
Commits on Jan 4, 2024
-
-
[editorial] Move keyword production to a better spot. Rephrase bool/k…
…eyword to include the # directly. Explicitly spell out the disallowed keywordish idents, and move where they appear. Rename numberish-ident to signed-ident (it's not numberish at all, is the point).
-
Commits on Jan 6, 2024
-
* Add newlines to some of the bare ident tests that were missing them * eof_after_escape.kdl is valid according to spec
Commits on Feb 8, 2024
Commits on Feb 9, 2024
Commits on Feb 15, 2024
-
Update tests/test_cases/expected_kdl/multiline_string_indented.kdl
Co-authored-by: Dani Smith <[email protected]>
-
Update tests/test_cases/expected_kdl/multiline_raw_string_indented.kdl
Co-authored-by: Dani Smith <[email protected]>
Commits on Feb 18, 2024
Commits on Mar 5, 2024
-
Co-authored-by: Bannerets <[email protected]>
-
Co-authored-by: Bannerets <[email protected]>
-
Co-authored-by: Bannerets <[email protected]>
Commits on Apr 1, 2024
Commits on Apr 2, 2024
Commits on Apr 3, 2024
Commits on Apr 17, 2024
Commits on Jun 13, 2024
-
Tweak rules for escaped whitespace in multi-line strings (#392)
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.
