vscode-styled-components

vscode-styled-components copied to clipboard

As discussed in #274, typescript-styled-plugin can be a useful tool, however the out-of-the-box config leaves something to be desired. Most notably, it flags valid css attributes like margin-inline as errors.

Similarly, many users will already rely on stylelint for this feature set. In addition to being more customizable, it definitely as the widest marketshare. No reason for these users to use two linters.

Lastly, whether performance reasons or sheer rebelliousness, some users won't necessarily want a css linter running.

Solution: We should have an option to switch between common linter config:

• typescript-styled-plugin
• stylelint
• (none)

Secondarily, an option to supply a global config file for the provided linter may be useful.