You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This "broke" during the big reshuffle made as part of hashicorp/hcl-lang#177 and hashicorp/hcl-lang#187. While from continuity perspective this could be seen as a bug, it was a decision to avoid the complexity - esp. related to handling of multi-line strings and leave out the functionality entirely.
So - from terraform-ls perspective this is a bug, but from hcl-lang perspective it's a missing feature.
Expected Behaviour
Completing just "" on attribute completion and triggering completion again
Bring all available backend names on expression completion
Context
This "broke" during the big reshuffle made as part of hashicorp/hcl-lang#177 and hashicorp/hcl-lang#187. While from continuity perspective this could be seen as a bug, it was a decision to avoid the complexity - esp. related to handling of multi-line strings and leave out the functionality entirely.
So - from
terraform-ls
perspective this is a bug, but fromhcl-lang
perspective it's a missing feature.Expected Behaviour
""
on attribute completion and triggering completion againProposal
We could pick one of the two routes:
LiteralValue{}
of string type, similarly to how we already implement it for boolean: https://github.com/hashicorp/hcl-lang/blob/0ab4d92a142f208f9ce72760818c357e9ddeb850/decoder/expr_literal_value_completion.go#L49-L52LiteralValue
withLiteralType
'sEnum
hcl-lang#260 and then implement completion based on that (which should be slightly easier)The text was updated successfully, but these errors were encountered: