berkus
/
kdl
mirror of https://github.com/kdl-org/kdl.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

- Removed tests that allowed empty strings as identifiers. 

- Edited SPEC.md to be clear about not allowing zero-length identifiers.
- Need to update grammar as well.
This commit is contained in:
Patitotective 2022-09-19 16:59:20 -05:00
parent c8dd45a0f1
commit 3989d37026
6 changed files with 3 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
SPEC.md
View File

@ -50,7 +50,7 @@ baz
Being a node-oriented language means that the real core component of any KDL Being a node-oriented language means that the real core component of any KDL
document is the "node". Every node must have a name, which is either a legal document is the "node". Every node must have a name, which is either a legal
[Identifier](#identifier), or a quoted [String](#string). [Identifier](#identifier) or a quoted [String](#string), this quoted string has to have more than 0 characters (`""` is not a valid string identifier).
The name may be preceded by a [Type Annotation](#type-annotation) to further The name may be preceded by a [Type Annotation](#type-annotation) to further
clarify its type, particularly in relation to its parent node. (For example, clarify its type, particularly in relation to its parent node. (For example,
@ -145,7 +145,7 @@ my-node 1 2 \ // comments are ok after \
### Property ### Property
A Property is a key/value pair attached to a [Node](#node). A Property is A Property is a key/value pair attached to a [Node](#node). A Property is
composed of an [Identifier](#identifier) or a [String](#string), followed composed of an [Identifier](#identifier) or a [String](#string) (this quoted string has to have more than 0 characters), followed
immediately by a `=`, and then a [Value](#value). immediately by a `=`, and then a [Value](#value).
Properties should be interpreted left-to-right, with rightmost properties with Properties should be interpreted left-to-right, with rightmost properties with
@ -220,7 +220,7 @@ or as a _context-specific elaboration_ of the more generic type the node name
indicates. indicates.
Type annotations are written as a set of `(` and `)` with a single Type annotations are written as a set of `(` and `)` with a single
[Identifier](#identifier) in it. Any valid identifier is considered a valid [Identifier](#identifier) or [String](#string) (this quoted string has to have more than 0 characters) in it. Any valid identifier is considered a valid
type annotation. There must be no whitespace between a type annotation and its type annotation. There must be no whitespace between a type annotation and its
associated Node Name or Value. associated Node Name or Value.

1
tests/test_cases/expected_kdl/blank_arg_type.kdl
View File

@ -1 +0,0 @@
node ("")10

1
tests/test_cases/expected_kdl/blank_node_type.kdl
View File

@ -1 +0,0 @@
("")node

1
tests/test_cases/expected_kdl/blank_prop_type.kdl
View File

@ -1 +0,0 @@
node key=("")true

1
tests/test_cases/expected_kdl/empty_quoted_node_id.kdl
View File

@ -1 +0,0 @@
"" "arg"

1
tests/test_cases/expected_kdl/empty_quoted_prop_key.kdl
View File

@ -1 +0,0 @@
node ""="empty"