Justin Chadwell fbb4f4dec8 bake: avoid nesting error diagnostics ... With changes to the lazy evaluation, the evaluation order is no longer fixed - this means that we can follow long and confusing paths to get to an error. Because of the co-recursive nature of the lazy evaluation, we need to take special care that the original HCL diagnostics are not discarded and are preserved so that the original source of the error can be detected. Preserving the full trace is not necessary, and probably not useful to the user - all of the file that is not lazily loaded will be eagerly loaded after all struct blocks are loaded - so the error would be found regardless. Signed-off-by: Justin Chadwell <me@jedevc.com>		2023-02-07 11:40:20 +00:00
..
hclparser	bake: avoid nesting error diagnostics	2023-02-07 11:40:20 +00:00
bake.go	lint: ban fmt.Errorf in preference of errors.Errorf	2023-02-01 10:31:01 +00:00
bake_test.go	bake: support null label value	2022-12-14 08:30:58 +01:00
compose.go	update github.com/compose-spec/compose-go to v1.9.0	2023-02-03 03:19:59 +01:00
compose_test.go	bake: support null arg value	2022-12-14 08:29:27 +01:00
hcl.go	bake: restrict target name	2022-01-26 10:29:21 +01:00
hcl_test.go	bake: avoid early-exit for resolution failures	2023-02-06 15:05:45 +00:00
remote.go	bake: fix loop references	2023-02-01 10:13:43 +00:00