-
Notifications
You must be signed in to change notification settings - Fork 57
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
Completion for a type which is an alias to some record type? #311
Comments
I double-checked and I found the autocompletion is actually provided by |
cristianoc
added a commit
that referenced
this issue
Nov 25, 2021
The current function to extract record types looks for a type definition, and expect it to be a record. The new one keeps on expanding type definitions until it finds a record. In this way, it handles type aliases. Fixes #311
cristianoc
added a commit
that referenced
this issue
Nov 25, 2021
The current function to extract record types looks for a type definition, and expect it to be a record. The new one keeps on expanding type definitions until it finds a record. In this way, it handles type aliases. Fixes #311
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Suppose we have the following code:
If I type
Js.log(x1.
, autocompletion is triggered and the fieldcontent
is suggested. However, if I typeJs.log(x2.
, autocompletion is not triggered.Is this an intended behavior? I think it would be more convenient if autocompletion is triggered for
x2
too.The text was updated successfully, but these errors were encountered: