Masayuki Morita

Thank you for reporting the issue. Yes, the address index expression hasn't been implemented yet.

The `locals.workload_1` is an attribute, not a block. We can get it with `hcledit attribute get locals.workload_1` ``` $ cat test.hcl | hcledit attribute get locals.workload_1 { vpc0 = {...

The hcledit depends on the `hclwrite` parser in the hcl library which is used by the `terraform fmt` command and is specialized for the token-based edit to preserve comments. However,...

Thank you for pointing out it. The hcledit uses a token based parser and actually doesn't know what type is correct in application schema, so you can set an object...

Thank you for opening this. It's a missing feature to add an element to list. To implement this, we need to a feature to hclwrite, which is a library we...

@bjornrog Thank you for reporting this! It looks a bug caused by a hack here due to the current limitation of the hcl library. https://github.com/minamijoyo/hcledit/blob/397e5f46bda35b45501b36b841afd8b9d683a0f4/editor/sink_attribute_get.go#L184-L205 I think it's hard to...

Hi @syphernl, Thank you for reporting this. In the HCL specification, `foo {}` is a block and `foo = {}` is an attribute with an object type. Note that `=`...

It's intentional because having multiple blocks as the same name is valid in the HCL specification and there is no way to check what is valid in the application level...

@mhennecke Thank you for reporting this! It should work as you expect, but it seems not. I think we cannot reuse the `findLongestMatchingBlocks` method as it is because removing a...

Hi @antonbabenko, Thank you for your proposal. It's not supported yet. I think the problem is not only for a new file, the root cause of this problem is that...