Skip to content

Commit 901cdf0

Browse files
authored
Add JSON syntax highlighting to README.md (#1070)
1 parent 518b271 commit 901cdf0

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

packages/vscode-tailwindcss/README.md

+4-4
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ An alternative to VS Code's built-in CSS language mode which maintains full CSS
3838

3939
Use the `files.associations` setting to tell VS Code to always open `.css` files in Tailwind CSS mode:
4040

41-
```
41+
```json
4242
"files.associations": {
4343
"*.css": "tailwindcss"
4444
}
@@ -48,7 +48,7 @@ Use the `files.associations` setting to tell VS Code to always open `.css` files
4848

4949
By default VS Code will not trigger completions when editing "string" content, for example within JSX attribute values. Updating the `editor.quickSuggestions` setting may improve your experience:
5050

51-
```
51+
```json
5252
"editor.quickSuggestions": {
5353
"strings": "on"
5454
}
@@ -168,13 +168,13 @@ By default the extension will automatically use the first `tailwind.config.{js,c
168168

169169
If your project contains a single Tailwind config file you can specify a string value:
170170

171-
```
171+
```json
172172
"tailwindCSS.experimental.configFile": ".config/tailwind.config.js"
173173
```
174174

175175
For projects with multiple config files use an object where each key is a config file path and each value is a glob pattern (or array of glob patterns) representing the set of files that the config file applies to:
176176

177-
```
177+
```json
178178
"tailwindCSS.experimental.configFile": {
179179
"themes/simple/tailwind.config.js": "themes/simple/**",
180180
"themes/neon/tailwind.config.js": "themes/neon/**"

0 commit comments

Comments
 (0)