v2.10.0

v2.10.0 (April 20, 2021)

Enhancements

• dynblock,hcldec: Using dynblock in conjunction with hcldec can now decode blocks with unknown dynamic for_each arguments as entirely unknown values (#461)
• hclsyntax: Some syntax errors during parsing of the inside of ${ ... } template interpolation sequences will now produce an extra hint message about the need to escape as $${ when trying to include interpolation syntax for other languages like shell scripting, AWS IAM policies, etc. (#462)

v2.9.1

Bugs Fixed

• hclsyntax: Fix panic for marked index value. (#451)

v2.8.2

Bugs Fixed

• hclsyntax: Fix panic for marked collection splat. (#436)
• hclsyntax: Fix panic for marked template loops. (#437)
• hclsyntax: Fix for expression marked conditional.(#438)
• hclsyntax: Mark objects with keys that are sensitive. (#440)

v2.8.1

Bugs Fixed

• hclsyntax: Fix panic when expanding marked function arguments. (#429)
• hclsyntax: Error when attempting to use a marked value as an object key. (#434)
• hclsyntax: Error when attempting to use a marked value as an object key in expressions. (#433)

v2.8.0

Enhancements

• hclsyntax: Expression grouping parentheses will now be reflected by an explicit node in the AST, whereas before they were only considered during parsing. (#426)

Bugs Fixed

• hclwrite: The parser will now correctly include the ( and ) tokens when an expression is surrounded by parentheses. Previously it would incorrectly recognize those tokens as being extraneous tokens outside of the expression. (#426)
• hclwrite: The formatter will now remove (rather than insert) spaces between the ! (unary boolean "not") operator and its subsequent operand. (#403)
• hclsyntax: Unmark conditional values in expressions before checking their truthfulness (#427)

v2.7.2

Bugs Fixed

• gohcl: Fix panic when decoding into type containing value slices. (#335)
• hclsyntax: The unusual expression null[*] was previously always returning an unknown value, even though the rules for [*] normally call for it to return an empty tuple when applied to a null. As well as being a surprising result, it was particularly problematic because it violated the rule that a calling application may assume that an expression result will always be known unless the application itself introduces unknown values via the evaluation context. null[*] will now produce an empty tuple. (#416)
• hclsyntax: Fix panic when traversing a list, tuple, or map with cty "marks" (#424)

v2.7.1

Bugs Fixed

• hclwrite: Correctly handle blank quoted string block labels, instead of dropping them (#422)

v2.7.0

Enhancements

• json: There is a new function ParseWithStartPos, which allows overriding the starting position for parsing in case the given JSON bytes are a fragment of a larger document, such as might happen when decoding with encoding/json into a json.RawMessage. (#389)
• json: There is a new function ParseExpression, which allows parsing a JSON string directly in expression mode, whereas previously it was only possible to parse a JSON string in body mode. (#381)
• hclwrite: Block type now supports SetType and SetLabels, allowing surgical changes to the type and labels of an existing block without having to reconstruct the entire block. (#340)

Bugs Fixed

• hclsyntax: Fix confusing error message for bitwise OR operator (#380)
• hclsyntax: Several bug fixes for using HCL with values containing cty "marks" (#404, #406, #407)

v2.6.0

Enhancements

• hcldec: Add a new Spec, ValidateSpec, which allows custom validation of values at decode-time. (#387)

Bugs Fixed

• hclsyntax: Fix panic with combination of sequences and null arguments (#386)
• hclsyntax: Fix handling of unknown values and sequences (#386)

v2.5.1

Bugs Fixed

• hclwrite: handle legacy dot access of numeric indexes. (#369)
• hclwrite: Fix panic for dotted full splat (foo.*) (#374)