270c60ca9a
Revert "Allow single-line comments with nothing after them. Fixes #318"
...
This reverts commit 652590fad3
2023-10-06 14:07:29 -07:00
54f5fc8025
Revert "Add vertical tab to whitespace characters. Fixes #331"
...
This reverts commit ef1bb689b0
2023-10-06 14:07:28 -07:00
ef1bb689b0
Add vertical tab to whitespace characters. Fixes #331
2023-10-06 13:58:35 -07:00
652590fad3
Allow single-line comments with nothing after them. Fixes #318
2023-10-06 13:56:03 -07:00
f3e5ff6027
Rearrange the number production to put decimal at the end
...
While the grammar makes no statements about match order, parsers pretty universally test for decimal last, after the other number productions, because `0b010` (/etc) can look like a `0` followed by garbage. Matching this order can reduce confusion.
Closes #330 .
2023-05-30 14:13:46 -07:00
a75ca13c15
Fix a typo in SPEC.md ( #323 )
2023-05-25 12:09:47 -07:00
0b99021180
Improvements to string naming consistency ( #299 )
...
This PR modifies string descriptions in SPEC.md to use more consistent language throughout, with the primary intention of removing long descriptions like "a property key is either an identifier or a string". There are no semantic changes to KDL here.
2022-09-20 17:29:59 -07:00
9daa2019f7
Fix RFC typo ( #276 )
...
The ``email`` field in Reserved Type Annotations for Strings refers to [RFC 5302](https://datatracker.ietf.org/doc/html/rfc5302 ), it should be [RFC 5322](https://datatracker.ietf.org/doc/html/rfc5322 ) instead.
2022-07-22 10:34:21 -07:00
b027d3a751
Remove children from node terminals ( #275 )
...
The grammar doesn't specify that children count
as node terminator, but the text does.
The following document would be valid per text,
but invalid per spec.
```kdl
node { child {} }
```
Fixes #274
2022-07-11 15:13:05 -07:00
fcd489afa6
Add more info about the hyphen character in identifiers ( #271 )
2022-04-25 10:04:28 -07:00
81a58e64ee
Mention multi-line comments in spec prose ( #263 )
2022-03-29 13:00:29 -07:00
3e915b5be3
Clarify the parsing of hostname and idl-hostname ( #248 )
...
Ref: #247
2022-02-19 02:06:54 -08:00
8976e2da68
Define `digit` in formal grammar ( #236 )
...
`digit` is used as a subtraction in bare-identifier, but never defined.
2022-02-19 02:06:17 -08:00
5a566ea5e3
Fix #212 by clarifying left/right ( #249 )
2022-02-19 02:04:38 -08:00
a1d85e9fe1
[editorial] tweak node-props-and-args grammar ( #240 )
...
* replaces a `foo foo*` with a `foo+`
* switches the name of the production to singular, since it only represents one prop/arg at a time
No normative changes intended.
2021-10-17 08:46:34 -07:00
296fe129e1
argument/property ordering clarification ( #206 )
2021-09-26 22:47:08 -07:00
5c4f83b824
Update line continuation wording ( #184 )
2021-09-19 16:28:25 -07:00
16269d4325
Prevent markdown from parsing []() as link ( #162 )
...
* Use same order from grammar definition
2021-09-15 18:26:50 -07:00
785abebfc5
fix(spec): Correct bom from U+FFEF to U+FEFF ( #153 )
2021-09-13 20:17:20 -07:00
f68137f526
slap a date on it
2021-09-11 21:08:09 -07:00
02c40c589d
bump version to 1.0.0 and add example with type annotations
2021-09-11 21:04:22 -07:00
f0bc492021
Add some more reserved type annotations ( #134 )
...
I think it would be useful to get these few more common data types into
For the decimal floating types, I referenced [this protobuf discussion](https://github.com/protocolbuffers/protobuf/pull/7039#issuecomment-679083593 ) and [this](https://github.com/googleapis/googleapis/blob/master/google/type/decimal.proto )
I'm not sure what to call out for the currency format, I can't find a standard for that yet. There's a [protobuf money type](https://github.com/googleapis/googleapis/blob/master/google/type/money.proto ) that's basically a ISO 4217 currency code plus a decimal number, but I don't really want to invent a suggested money format if there's a real one out there somewhere.
For this PR, can we just leave it TBD in order to reserve the type keyword?
2021-09-11 20:46:32 -07:00
0cdda0b711
Disallow ws after (type) in grammar ( #138 )
...
Fixes: https://github.com/kdl-org/kdl/issues/131
2021-09-10 17:11:41 -07:00
f1941b53d3
Allow node names to have type annotations. Bump JiK to take advantage of this. ( #132 )
2021-09-08 18:03:13 -07:00
ede621807e
Fix multi-line-comment grammar ( #130 )
...
Fix https://github.com/kdl-org/kdl/issues/128
2021-09-05 12:12:35 +02:00
dec2565a17
fix typos ( #129 )
2021-09-03 08:02:49 -07:00
cbb500a4ac
allow /- to cross linespaces ( #127 )
...
Ref: https://github.com/kdl-org/kdl/issues/121
2021-09-02 15:29:25 -07:00
6b4d0ea030
allow eof termination for single line comments ( #126 )
2021-09-02 15:25:13 -07:00
2e42c4c0ec
Change URIs to URLs for clarity ( #125 )
2021-09-02 15:10:03 -07:00
a44fcbb1d4
add type annotation info to spec ( #123 )
...
Fixes: https://github.com/kdl-org/kdl/issues/106
2021-09-02 09:23:51 -07:00
7c54aae64f
actually add child node spec to spec itself
...
Fixes: https://github.com/kdl-org/kdl/issues/59
2021-08-31 23:08:12 -07:00
129812543f
prevent the three "keywords" from being used as bare identifiers ( #117 )
...
Fixes: https://github.com/kdl-org/kdl/issues/114
2021-08-31 21:47:59 -07:00
37c0a38baa
allow _ in post-decimal-point section ( #118 )
...
Fixes: https://github.com/kdl-org/kdl/issues/69
2021-08-31 20:39:17 -07:00
3f739cad42
make / illegal in identifiers
...
Fixes: https://github.com/kdl-org/kdl/issues/75
2021-08-31 20:09:45 -07:00
04a84a72ec
link to other specs
2021-08-31 19:38:26 -07:00
34c6592f09
remove () from identifiers so we can use it for KQL ( #108 )
2021-08-31 17:09:57 -07:00
9e35601c91
Partially revert #99 ( #100 )
...
6704988633
2021-08-24 14:57:03 -07:00
6704988633
identifiers should never look like numbers ( #99 )
2021-08-24 09:10:08 -07:00
5883435297
fix(grammar): allow whitespace before a node-terminator ( #98 )
...
kudos to @lucretiel for spotting this one.
2021-08-21 18:05:53 -07:00
e7147cf4ac
Fixed inconsistency between spec wording and BNF ( #88 )
2021-04-18 20:19:34 -07:00
15aff6a309
Added optional sign to all number syntaxes ( #87 )
2021-04-18 20:19:21 -07:00
9ceb0ed8d4
Possible typo in "Escapes" table ( #72 )
...
The maximum unicode code point is `10FFFF` but in the escapes table it states code points can only go up to `10FFF`. I think this is an error, since most emojis are well above that number, and other languages allow escapes up to `10FFFF`
2021-01-11 12:08:03 -08:00
1f293c280b
Add forwardlash to escapes table ( #73 )
...
I noticed this was a valid escape char in the rust implementation. Not sure if this was intended.
2021-01-11 12:07:28 -08:00
1cf1fd0597
Correct description of the raw string format ( #71 )
2021-01-08 21:09:11 -08:00
89b52b2145
Fill in string escapes table ( #60 )
2020-12-29 11:27:37 -08:00
3da011acbc
Update SPEC.md ( #57 )
...
this does a few things with identifiers and strings:
- removes `"` from the set of identifier characters, to prevent ambiguity with string
- adds `bare-identifier` and `escaped-string` non-terminals (i think less mixing of terminal/non-terminal is easier to read?)
- moves string ahead of bare-identifier in identifier, for easier implementation with ordered-choice parsers
- moves raw-string into string, so you can have raw-string identifiers
2020-12-26 18:03:32 -08:00
81fad70856
Fixed escape table formatting ( #44 )
2020-12-22 14:33:39 -08:00
cf341eac91
more blabber
2020-12-18 22:58:09 -08:00
60bcfdf926
require terminator after node-children too
2020-12-18 22:56:27 -08:00
b30b0cf93a
messing with nodes some more
2020-12-18 21:32:40 -08:00
Tab Atkins-Bittner
Evgeny
Nathan West
oledfish
Bram Gotink
Jelle Besseling
Sebastian Paarmann
Christopher Durham
Ben Reinhart
Chris Morgan
Kat Marchán
Eric Sampson
Lars Willighagen
Jo Liss
Serafina Brocious
Daniel Smith
Hannah Kolbeck
hclarke