Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve rendering of complex types in hover #270

Open
radeksimko opened this issue Apr 25, 2023 · 0 comments
Open

Improve rendering of complex types in hover #270

radeksimko opened this issue Apr 25, 2023 · 0 comments

Comments

@radeksimko
Copy link
Member

radeksimko commented Apr 25, 2023

Context

Currently we provide relatively inconsistent hover data for various complex types:

Screenshot 2023-04-25 at 15 56 34

i.e. we render nested objects with the appropriate nesting, markdown syntax etc. but we leave all other types to be rendered as "human friendly" names.

variable "test" {
  type = object({
    str = string
    num = number
    bl  = bool

    bar = map(string)
    lst = list(string)
    set = set(string)
    tpl = tuple([number, string])

    baz = object({
      noot = string
    })
  })
}

output "test" {
  value = var.test
}

Proposal

Consider rendering all types as valid typeexpr syntax, e.g. map(string) instead of map of string or list(bool) instead of list of bool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant