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
Extension: Typescript Language Features Feature: Autocompletion of Template Literal Types with unresolved types.
Hi,
Currently the autocompletion for template literal types stops working as soon as an ambiguous type is used in the template, like number or string.
My idea is, that instead of proposing nothing at all, the autocompletion feature can be extended to propose a snippet with a template literal string and tabstops for the parameters or alternatively a normal string. String unions could be replaced with choices. The end result after selecting the completion would look like something like that:
This could be for example helpful with APIs that typed their Ressource pathes using parametrized template literals.
The text was updated successfully, but these errors were encountered:
Extension: Typescript Language Features
Feature: Autocompletion of Template Literal Types with unresolved types.
Hi,
Currently the autocompletion for template literal types stops working as soon as an ambiguous type is used in the template, like number or string.
My idea is, that instead of proposing nothing at all, the autocompletion feature can be extended to propose a snippet with a template literal string and tabstops for the parameters or alternatively a normal string. String unions could be replaced with choices. The end result after selecting the completion would look like something like that:
This could be for example helpful with APIs that typed their Ressource pathes using parametrized template literals.
The text was updated successfully, but these errors were encountered: