Package.xml for Nested LWC Components

[OPutria]

Hello team,
I'd like to propose a feature that would greatly improve the developer experience for projects using nested Lightning Web Components.

The Problem
Currently, when working with nested LWC components like force-app/main/default/lwc/common/lwc/customInput, the sfdx-delta tool doesn't seem to generate a valid package.xml file automatically.
If I try to generate package.xml, I will see something like

<types> <members>common</members> <name>LightningComponentBundle</name> </types>
Where I expect something like the example below to be able to deploy it:
<types> <members>customInput</members> <name>LightningComponentBundle</name> </types>

[scolladon]

Hi @OPutria !

Thanks for raising your concerns about this feature and thanks for contributing in making this project better!

We have build something about this behaviour a few releases ago : #1087
=> What version of SGD are you using ?

Could you share more information about how to reproduce this issue please ?
You can either describe what commit content I should create inside a repository, or you could also fork the reproduction playground, create a branch, write the necessary commit to reproduce and share that branch here.
And give me the commands to run with sgd to reproduce the issue.

[OPutria]

Hi @scolladon, sorry, it seems I used a little older version and didn't know about this update. I updated the plugin, and it works as expected. Thanks, it is such a cool and necessary feature 🔥