feat: add VS Code configuration defaults #947
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
eltigerchino
changed the title
thecrypticace
added a commit
that referenced
this pull request
Nov 11, 2024
) This is an alternative design to part of #947. In that PR we'd be setting a default for *all* CSS files whether they're in a Tailwind CSS project or not. Instead we: 1. Detect that an opened CSS file is in a Tailwind CSS project and switch the language to `tailwindcss`. If you manually set it back to the CSS language we won't switch it back to `tailwindcss` again until you reload VSCode. 2. Switch any documents after the language server has found a project. This ensures that when starting a new project and you've created a CSS file typing `@import "tailwindcss"` and saving it will then switch the language to `tailwindcss`.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The recommended VS code settings can be provided by default when the extension is installed using the configuration defaults contribution point in the extension
package.json. This would mean less setup for users who install the extension and benefits people who may have missed reading the README first (sadly I was one of those people).