Re: [bitbake-devel] [PATCH] bitbake-setup: preserve VSCode extension recommendation

Hi Alex,

Thanks, you're right to question this.

I went back through the history of the VSCode workspace support and I
can't establish a convincing real-world case for this patch.

The workspace feature was introduced with the
`yocto-project.yocto-bitbake` recommendation already present, and the
original test explicitly verifies it. I also couldn't find an
established contract that treats `extensions.recommendations` as
managed state that bitbake-setup should restore after a user changes
it.

So the scenario in my test was effectively assuming policy that
bitbake-setup doesn't currently define.

Please disregard this patch. Thanks for catching that.

Giancarlo

On Wed, 19 Aug 2026 10:32:26 +0200, Alexander Kanavin
<[email protected]> wrote:
> On Tue, 18 Aug 2026 at 22:37, Giancarlo Cicellyn Comneno via
> lists.openembedded.org
> <[email protected]> wrote:
> > configure_vscode() initializes the Yocto BitBake extension recommendation
> > when creating a new workspace. When an existing workspace is loaded, its
> > extensions section replaces that initial value, so the managed
> > recommendation can disappear.
>
> The existing workspace was also created by bitbake-setup, so what is
> the scenario where it doesn't have the yocto-bitbake extension and it
> needs to be re-added?
>
> Alex