| commit | 277e15c4a1404758f64b99daf45e27d749e8b0eb | [log] [tgz] |
|---|---|---|
| author | Adam Barth <abarth@google.com> | Wed May 08 22:31:27 2024 +0000 |
| committer | Adam Barth <abarth@google.com> | Wed May 08 22:31:27 2024 +0000 |
| tree | 829fc8820e49573a9888321012cfc4edb5fbc909 | |
| parent | a372a829ada57e0ffb6b0b83e34d5fe414734b47 [diff] |
[bug] Don't rely on findFiles If the user has an exclusion pattern set for `.*` or `out`, then the `findFiles` function won't be able to find the `.fx-build-dir` or the `tests.json` file. Instead, we can just try to read those files directly. Change-Id: I9d66047ba3e5f2b63db6fd0fc872cc753191fffd Reviewed-on: https://fuchsia-review.googlesource.com/c/vscode-plugins/+/1044800 Kokoro: Kokoro <noreply+kokoro@google.com> Reviewed-by: Jacob Rutherford <jruthe@google.com>
Implements the commonly needed functionality for Fuchsia development.
Select a Fuchsia device using the Device Selector in the bottom toolbar:
Select “Show log for device name” from quick picker:
View the logs:
Select the “Testing” tab from the left navigation bar and view the list of tests in your current build configuration:
Click the “Run Test” or “Debug Test” button to run or debug the test. Double-click the test to jump to the BUILD.gn that defines the test.
Select the “Run and Debug” tab from the left navigtaion bar and expand the “Fuchsia Components” panel to view the components running on the device:
Click the “Attach Debugger” button to attach the debugger to the component. Set a breakpoint by clicking to the left of a line of source code to stop the component on that line of code.
Click a component to show more information about that component.
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/ffxUse 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.