made error/warning button push more obvious
This commit is contained in:
1 parent
5ae930c710
commit
97501875b8
4 files changed
+37
-1
No files matched your search
@@ -0,0 +1,25 @@
|
||||
# VS Code extension instructions
|
||||
|
||||
## VS Code extension
|
||||
|
||||
After every change to this extension, complete the update by compiling,
|
||||
packaging, and installing the extension in the connected VS Code environment.
|
||||
This includes changes limited to the Log Explorer HTML, CSS, or JavaScript.
|
||||
|
||||
- Keep the current extension version unless the user explicitly requests a
|
||||
version change. Do not bump `package.json` or `package-lock.json` automatically.
|
||||
- From this directory, run `npm run compile` and the checks appropriate to
|
||||
the change. Report any existing test failures separately.
|
||||
- Package with `vsce package --out vscode-appdaemon-<current-version>.vsix`,
|
||||
using the installed or cached `@vscode/vsce` CLI when available. Overwrite the
|
||||
existing VSIX for that version; never pass a version increment to `vsce`.
|
||||
- Install that exact VSIX using
|
||||
`code --install-extension ./vscode-appdaemon-<current-version>.vsix --force`.
|
||||
- Confirm the installed version with `code --list-extensions --show-versions`.
|
||||
When possible, verify the installed changed files match the packaged files.
|
||||
- Tell the user to reload the VS Code window to activate the update. If the
|
||||
connected CLI is unavailable or installation fails, report that limitation
|
||||
clearly and provide the generated VSIX path; do not claim it was installed.
|
||||
|
||||
The user's request authorizes this routine local build and installation after
|
||||
extension edits. Do not ask for additional conversational confirmation.
|
||||
Reference in new issue
Block a user