Bitbake recipe view #60
Conversation
deribaucourt
force-pushed
the
bitbake-recipe-view
branch
3 times, most recently
from
585149d to
f422fe5
Compare
|
|
deribaucourt
force-pushed
the
bitbake-recipe-view
branch
from
01c527d to
ac96167
Compare
|
So I have this error when clicking the refresh icon (and on startup too). Is it trying to find the oe-init-build-env file in the extension instead of the workspace folder? |
| done() | ||
| }) | ||
|
|
||
| // eslint-disable-next-line @typescript-eslint/no-unused-vars |
There was a problem hiding this comment.
I'm curious about these esling-disable. Do they have purpose,how you just forgot to remove them?
There was a problem hiding this comment.
All of them are required and valid exceptions to some eslint rules.
This one in particular is gone with one of your other suggestions being implemented.
@WilsonZiweiWang It takes the file from the bitbake settings. Can you share a screenshot of your workspace configuration for the bitbake extension? |
deribaucourt
force-pushed
the
bitbake-recipe-view
branch
2 times, most recently
from
8f912da to
5d5c9e5
Compare
This new activity panel will allow users to quickly see the list of recipes in the current workspace. More features will be added in this PR.
In order not to collide with the BitbakeProjectScanner might use for representing recipes.
We'll need to share the scan results with the language client extension. Prepare for this by moving the types into the common library.
A language server notification is now emitted to the client. It will be possible to use the scan results to populate the Bitbake recipes view.
Using the results from the bitbake scan, display the main recipe source file in the recipe view.
Example code triggering this:
```
python do_fetch:append() {
not python code
}
```
This stops showing .bbappend files not relevant to the recipe version that is used.
The tests have a complex mock infrastructure to generate the tree view. It then checks that the tree view has all the elements we expect.
Previously, the constructor was called with side effects and then the variable was never used. This could look like an unused variable to linters.
If the parsing errors test was fired before the other test, the build directory was missing, resulting in random failures: EntryNotFound (FileSystemError): Error: ENOENT: no such file or directory, open '/home/runner/work/vscode-bitbake/vscode-bitbake/integration-tests/project-folder/build/conf/bblayers.conf'
deribaucourt
force-pushed
the
bitbake-recipe-view
branch
from
a85af39 to
99d3ca3
Compare
|
That's because you are using relative paths without ${workspaceFolder}. However it should behave the same between the scanner and the tasks. I'll file a bug to address this. Is it ok if we do that in a separate PR? @WilsonZiweiWang |
Sounds good. |
No description provided.