Describe the bug
After creating an alias of a table, ---@alias foo {name: value} that is, and using that alias as a function param/return, the language server seems to not be able to recognize what type is it, reporting back any as the type.
In the above example, typing a table as the input anyways, and then pressing ctrl + space does show the right fields:
If the said type was used directly instead of creating it as an alias, it semi-works:
Although, it again never suggests the table fields until you explicitly do type an empty table {} and then press ctrl + space (As shown previously).
To Reproduce
See above screenshots.
Expected behavior
- The type is reported as
table or as {name: value}.
- An auto-completion shows up when one types down
{} in-place of the table type. Or
- An auto-completion shown up similar to the one for
fun() types.
Environment:
- OS: Linux, Fedora.
- Client: VSCode, latest.
- Version: 3.2.3
Describe the bug
After creating an alias of a table,
---@alias foo {name: value}that is, and using that alias as a function param/return, the language server seems to not be able to recognize what type is it, reporting backanyas the type.In the above example, typing a table as the input anyways, and then pressing
ctrl + spacedoes show the right fields:If the said type was used directly instead of creating it as an alias, it semi-works:
Although, it again never suggests the table fields until you explicitly do type an empty table
{}and then pressctrl + space(As shown previously).To Reproduce
See above screenshots.
Expected behavior
tableor as{name: value}.{}in-place of the table type. Orfun()types.Environment: