webview*s*: plural words are hard edition

When we switched to esbuild, the naming pattern for webviews went from
`webview-foo.js` to `webviews-foo.js`, but the logging provider was
accidentally (oops) not updated.

This fixes that.  Thanks to amyhu@ for catching this.

Change-Id: Ieb97f86472fad5b4f5311e64bfdd143d0784c6c5
Reviewed-on: https://fuchsia-review.googlesource.com/c/vscode-plugins/+/714224
Reviewed-by: Amy Hu <amyhu@google.com>
Kokoro: Kokoro <noreply+kokoro@google.com>
1 file changed
tree: 3fb88466e66952103c9d3017826bb42258865be8
  1. .ci/
  2. .kokoro/
  3. .vscode/
  4. docs/
  5. media/
  6. resources/
  7. src/
  8. syntax/
  9. testdata/
  10. webviews/
  11. .eslintrc.json
  12. .gitignore
  13. .vscodeignore
  14. AUTHORS
  15. build-helpers.mjs
  16. build.mjs
  17. BUILDING.md
  18. CONTRIBUTING.md
  19. LICENSE
  20. OWNERS
  21. package-lock.json
  22. package.json
  23. PATENTS
  24. README.md
  25. THIRD_PARTY_NOTICES.txt
  26. TROUBLESHOOTING_ZXDB.md
  27. tsconfig.json
README.md

Fuchsia extension for VS Code

This VS Code extension implements the commonly needed functionality for Fuchsia development.

This is a Work In Progress Currently supporting:

  • Interacting with the fuchsia target device.
    • Setting the default target.
    • Sending commands to the target.
  • Debugging C/C++ components.
  • Filtering and listening to target logs.

FFX path settings

The FFX tool path can be set under Settings > Extensions > Fuchsia SDK. If this path is not set, the extension will automatically search for it at:

  • ./tools/ffx
  • ./.jiri_root/bin/ffx

Recommended extensions

Contributing

Issues/feedback

  • Please report issues/feedback here.

Legal Notice

Use of the Fuchsia core developer tools is subject to the Google Terms of Service. The Google Privacy Policy describes how data is handled in your use of this service.