Add loose autocomplete for common config values #19592
Replies: 4 comments 6 replies
-
|
Where do you use |
Beta Was this translation helpful? Give feedback.
-
|
when a user is using webpack and creating a webpack.config.js file. |
Beta Was this translation helpful? Give feedback.
-
|
Please don't use |
Beta Was this translation helpful? Give feedback.
-
|
I gave a correct examples of using webpack types in a different answer in this thread |
Beta Was this translation helpful? Give feedback.
-
|
My bad. of course output.publicPath is just one example, there are many cases that could benefit from loose autocomplete making webpack easier to configure. |
Beta Was this translation helpful? Give feedback.
-
|
I think you need to open an issue in autocomplete plugin of your IDE, it should provide ability to get known string values |
Beta Was this translation helpful? Give feedback.
-
|
I am not using a plugin. That is just vs code's built in typescript autocomple. I don't need to change vs code. I just need to change the type |
Beta Was this translation helpful? Give feedback.
-
vscode using - https://github.com/microsoft/vscode/tree/main/extensions/typescript-basics and https://github.com/microsoft/vscode/tree/main/extensions/typescript-language-features and it should be improved from their side |
Beta Was this translation helpful? Give feedback.
-
|
Do you know an ide that can show autocomplete for a type like : |
Beta Was this translation helpful? Give feedback.
-
|
At least it can show |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Feature request
What is the expected behavior?
when I am configuring my webpack, some values are of type string because they accept all strings. however, there are special cases where a value will have unique behavior.
A great example of this is output.publicPath. it is of type string but can also accept 'auto' for a specific use case.
I want to have autocomplete for auto while also letting the user pass any string.
What is motivation or use case for adding/changing the behavior?
Better DX. not requiring the developer to check the docs for common values. reduces typos.
How should this be implemented in your opinion?
In typescript, the following type:
type example= 'auto' | (string & {})will allow all strings but will still autocomplete 'auto'.
here is a simple example I created.
If you would will like, I can add autocomplete for more config values
Are you willing to work on this yourself?
yes
Beta Was this translation helpful? Give feedback.
All reactions