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
It would be super cool if in the future lsp could auto complete the available methods that are registered for a given type if one types the object name and then a pipe operator.
Then a menu pops up with a list of the available methods for type user. Eg. here set_id and set_name
This feature would then give a similar experience as encapsulated OOP frameworks where typing the access operator on an object (like . in python classes) would give a list of available properties/methods for said object.
For me this would also solve one of the fundamental issues that I have with S3. Namely that I have to know the available generics for a given class off the top of my head.
(ps. I know that currently the lsp does not have an autocomplete feature. But once we get there it would be cool if the above described functionality is also added :) )
The text was updated successfully, but these errors were encountered:
It would be super cool if in the future lsp could auto complete the available methods that are registered for a given type if one types the object name and then a pipe operator.
Eg. from the S3 method example: https://vapour.run/docs/example-s3. It would be super cool if I type:
Then a menu pops up with a list of the available methods for type
user
. Eg. hereset_id
andset_name
This feature would then give a similar experience as encapsulated OOP frameworks where typing the access operator on an object (like
.
in python classes) would give a list of available properties/methods for said object.For me this would also solve one of the fundamental issues that I have with S3. Namely that I have to know the available generics for a given class off the top of my head.
(ps. I know that currently the lsp does not have an autocomplete feature. But once we get there it would be cool if the above described functionality is also added :) )
The text was updated successfully, but these errors were encountered: