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.
See discussion on #42
It turns out that you can include recommended extensions directly in the .code-workspace file, so I didn't need to add a .vscode/extensions.json file.
To test this:
@markw65/peggy
, and checked outorigin/peggy-code-workspace
.npm install
, then opened the peggy folder from vscode-insiders.generate-js.js
, and made some changes that eslint didn't like, and hit Shift-Option-F to format, and it fixed them for me, without modifying the rest of the file.defaulltFormatter
toTypescript and Javascript Language Features
in thepeggy
folder. This created a .vscode/settings.json file (which was hidden from git by the new .gitignore). I formattedgenerate-js.js
again, and it changed lots of things in ways that lint didn't like (so that formatter isn't actually useful, but demonstrates that people can still choose to use something other than the default).Given that settings can be overridden via .vscode/settings.json, I'm inclined to turn on
Format on Save
inpeggy.code-workspace
too.