-
-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve the workspace #179
Changes from 2 commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,6 @@ | ||
{ | ||
// Configure file associations to languages (e.g. `"*.extension": "html"`). These have precedence over the default associations of the languages installed. | ||
"files.associations": { | ||
"*.es": "javascript" | ||
} | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,3 +5,30 @@ Scripts used for configuring server nodes | |
## `nginx` | ||
|
||
nginx setup. Derived from [`whatwg/misc-server`](https://github.com/whatwg/misc-server) | ||
|
||
## `vscode` | ||
|
||
1. CTRL+SHIFT+P, search for "preferences open settings (JSON)" | ||
2. Open the "Workspace settings" tab | ||
3. Add the property "files.assiciations" if not present or extend it with the value "*.es": "javascript" | ||
|
||
Should looks like | ||
|
||
```javascript | ||
"files.associations": { | ||
"*.es": "javascript" | ||
} | ||
``` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. EASY PEASY @rianby64. This is great. Now where it should go see above. But wherever it goes this is great. |
||
|
||
or if your workspace settings is empty then, put the following | ||
|
||
```javascript | ||
{ | ||
// Configure file associations to languages (e.g. `"*.extension": "html"`). These have precedence over the default associations of the languages installed. | ||
"files.associations": { | ||
"*.es": "javascript" | ||
} | ||
} | ||
``` | ||
|
||
The result of the steps above are in the file `.vscode/settings.json`. |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -56,7 +56,6 @@ | |
"postcss-cli": "*", | ||
"autoprefixer": "*", | ||
"browser-sync": "*", | ||
"devtools-terminal": "*", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Bad news. If you rely on "devtools-terminal" then please, check the following:
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @rianby64 EXACTLY. Let's kill it with fire. To be honest it only was around when I was testing VIM in browser. I'm going to go ahead and merge this. |
||
"postcss-custom-properties": "*" | ||
}, | ||
"dependencies": { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this section necessary to add in addition to the config file?
if so, does it really belong in the main README or could it go into a separate doc page?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm @brandondees @rianby64 you both are right. It IS part of "configuration" per say. The thought was anything "configure" related stuff goes in
/configure
. But that is more internal dev related (perhaps shouldn't be?). Really was just a place I could quarantine the "This is how you get nginx to work for WHATWG" code I got fromWHATWG/meta
when we did nginx.IMHO this documentation should be as close to introduction as possible. Perhaps an IDE section in main README.md? /cc @tmornini
In addendum i'll add what I did for VIM.
Thanks for this @rianby64