-
Notifications
You must be signed in to change notification settings - Fork 581
Comparing changes
Open a pull request
base repository: hashicorp/hcl
base: v2.20.0
head repository: hashicorp/hcl
compare: main
- 17 commits
- 26 files changed
- 7 contributors
Commits on Mar 12, 2024
-
feat: return ExprSyntaxError instead of nil when expression parsing f…
…ails for namespaced functions
Configuration menu - View commit details
-
Copy full SHA for 1cbb0d4 - Browse repository at this point
Copy the full SHA 1cbb0d4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 53ee54e - Browse repository at this point
Copy the full SHA 53ee54eView commit details
Commits on Mar 13, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 54e4175 - Browse repository at this point
Copy the full SHA 54e4175View commit details -
Configuration menu - View commit details
-
Copy full SHA for cc3af98 - Browse repository at this point
Copy the full SHA cc3af98View commit details -
Merge pull request #668 from hashicorp/add-expr-syntax-error
add `ExprSyntaxError`
Configuration menu - View commit details
-
Copy full SHA for 5160967 - Browse repository at this point
Copy the full SHA 5160967View commit details
Commits on Mar 14, 2024
-
Standardize on only two value dumping/diffing libraries
Due to the quite messy heritage of this codebase -- including a large part of it being just a fork of my earlier personal project ZCL -- there were many different conventions for how to pretty-print and diff values in the tests in different parts of the codebase. To reduce the dependency sprawl, this commit now standardizes on: - github.com/davecgh/go-spew for pretty-printing - github.com/google/go-cmp for diffing These two dependencies were already present anyway, are the most general out of all of the candidates, and are also already in use by at least some of HCL's most significant callers, such as HashiCorp Terraform. The version of go-cmp we were previously using seems to have a bug that causes the tests to crash when run under the Go race detector, so I've also upgraded that dependency to latest here to clear that bug.
Configuration menu - View commit details
-
Copy full SHA for 2a0a3f0 - Browse repository at this point
Copy the full SHA 2a0a3f0View commit details
Commits on Mar 26, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 303be61 - Browse repository at this point
Copy the full SHA 303be61View commit details
Commits on Apr 22, 2024
-
Add additional function for parsing traversals with [*] keys (#673)
* Add additional function for parsing traversals with [*] keys * add more context around skipped test cases
Configuration menu - View commit details
-
Copy full SHA for f7cd61a - Browse repository at this point
Copy the full SHA f7cd61aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 1c5ae8f - Browse repository at this point
Copy the full SHA 1c5ae8fView commit details
Commits on May 8, 2024
-
github: Pin action refs to latest trusted by TSCCR (#677)
Co-authored-by: hashicorp-tsccr[bot] <hashicorp-tsccr[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 4521ae9 - Browse repository at this point
Copy the full SHA 4521ae9View commit details -
Configuration menu - View commit details
-
Copy full SHA for bf54697 - Browse repository at this point
Copy the full SHA bf54697View commit details
Commits on May 9, 2024
-
hclsyntax: Don't panic if splat operand is unknown and marked
We were calling .Range() on any unknown sourceVal, without first checking whether it was marked. That method panics if called on a marked value, so we need to strip that off first. While testing this I found some return paths that weren't properly transferring the source value's marks to the output, and so this also addresses those so that all return paths preserve whatever markings are present on the source value. In particular, if a non-list/set/tuple value gets "upgraded" into a tuple then we must transfer its marks onto the tuple, because the decision about constructing that value was based on characteristics of the source value.
Configuration menu - View commit details
-
Copy full SHA for bc75765 - Browse repository at this point
Copy the full SHA bc75765View commit details -
dynblock: Preserve marks from for_each expression into result
Previously if the for_each expression was marked then expansion would fail because marked expressions are never directly iterable. Now instead we'll allow marked for_each and preserve the marks into the values produced by the resulting block as much as we can. This runs into the classic problem that HCL blocks are not values themselves and so cannot carry marks directly, but we can at least make sure that the values of any leaf arguments end up marked.
Configuration menu - View commit details
-
Copy full SHA for 9a64c17 - Browse repository at this point
Copy the full SHA 9a64c17View commit details -
hcldec: Allow body-derived values to be marked
Similar to the previously-added UnknownBody, the new optional interface MarkedBody allows hcl.Body implementations to suggest a set of marks that ought to be applied to any value that's generated to represent the content of that body. The dynblock extension then uses this to get hcldec to mark the whole object representing any block that was generated by a dynamic block whose for_each was marked, for a better representation of the fact that a block's existence was decided based on a marked value.
Configuration menu - View commit details
-
Copy full SHA for 318bbfe - Browse repository at this point
Copy the full SHA 318bbfeView commit details -
Configuration menu - View commit details
-
Copy full SHA for 212a40e - Browse repository at this point
Copy the full SHA 212a40eView commit details
Commits on Jun 14, 2024
-
github: Pin action refs to latest trusted by TSCCR (#683)
Co-authored-by: hashicorp-tsccr[bot] <hashicorp-tsccr[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for f7e093a - Browse repository at this point
Copy the full SHA f7e093aView commit details
Commits on Jun 19, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 360ae57 - Browse repository at this point
Copy the full SHA 360ae57View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v2.20.0...main