| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Object elements can be separated by comma or newline
|
|
|
|
Update spec.md to avoid suggesting ! is a binary operator
|
|
Co-authored-by: kmoe <5575356+kmoe@users.noreply.github.com>
|
|
|
|
"within within" should be "within"
|
|
|
|
The current spec appears to suggest that the bang is a binary operator, which would enable
expressions such as `foo ! bar`.
https://github.com/hashicorp/hcl/blob/main/hclsyntax/parser.go#L1070 seems to suggest this is only
a unary operator.
|
|
Update spec.md
|
|
|
|
In the text talking about how to resolve the ambiguity between "for"
expressions and values/keys called "for" there was previously an incorrect
statement about the behavior of "(for)" as an object key.
That situation causes HCL to take the value of a variable named "for".
To get the literal string "for" we must instead write the name in quotes,
similarly to how we'd represent a key string that includes characters
which HCL doesn't admit into an identifier.
|
|
Fix inconsistent vars
|
|
To allow easir adaptation of data already serialized as JSON, HCL native
syntax allows both equals signs _and_ colons for object constructors.
This was already implemented, but not reflected in the pseudo-BNF in
the specification.
|
|
|
|
This changed during development as we iterated on the prototype, but the
spec is lagging behind.
|
|
The main HCL package is more visible this way, and so it's easier than
having to pick it out from dozens of other package directories.
|
