-
-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LWC component templates issue when generating the force-app delta #414
Comments
Hi @pibenett! Thanks for raising this issue and thanks for contributing in making this project better! Do you know if this issue was already present in |
@scolladon We had a similar issue with the LWC components getting identified as part of the delta but the js-meta.xml files were being excluded from a pr validation or deployment as well as an experience site failing validation/deployment due to it not pulling in the required folders. We reverted to v5.8.0 and the issue is not happening now on either. experience site error - Site.com | We are missing the metadata file in your bundle and are unable to deploy your sites. Update External_Customer_Portal and try again. lwc error - An object 'xxxClearance' of type LightningComponentBundle was named in package.xml, but was not found in zipped directory Only this would pull in with v5.10.0 if committing the .js component in a PR or release: /home/vsts/work/1/s/salesforce/changed-sources/salesforce/force-app/main/default/lwc/xxxClearance: v5.8.0 pulls this back in the delta when just the .js component is committed: /home/vsts/work/1/s/salesforce/changed-sources/salesforce/force-app/main/default/lwc/xxxClearance: |
Hi @br0bison! Thank you for your help on this one. I'll cook a fix in the coming days and let you know. |
Duplicate of #413 |
Hi @scolladon Sorry I did not mentioned it but indeed I'm running the 5.10.0 (latest-rc) and did not try with the 5.8.0 yet. Comparing to the #413, my delta folder is created well but on the other hand I had a kind of similar issue as @br0bison where I had to add manually the .site-meta.xml file in my delta generated experiences folder for my LWR site. |
We have a fix cooking here Could you try the PR with your real use case and see if it fixes the issue please ? |
We just released the version $ sfdx plugins:install sfdx-git-delta@latest-rc Do not hesitate to create an issue if anything goes wrong using it. |
@scolladon Receiving an error when trying to pull in metdata for a change to an experience cloud site still. Error We are missing the metadata file in your bundle and are unable to deploy your sites. Update External_Customer_Portal and try again The LWC components didn't have errors and looks to pull in all of the js-meta.xml files as required. |
I reopen the issue then Thanks @br0bison, great feedback |
v5.8.0 build file.txt Here are my build files for the experience cloud site components as a comparison between the two. I ran a compare in ultraedit and this one component is missing in latest-rc. |
We just released the version 5.10.2 $ sfdx plugins:install sfdx-git-delta@latest-rc Do not hesitate to create an issue if anything goes wrong using it. |
Hello Sebastien
What is the problem?
The --generate-delta don't generate the full LWC component when this one has a templates sub folder in it.
What is the parameter and the value you used with it?
sfdx sgd:source:delta --to "origin/release/v2023.01" --from "origin/master" --output changed-sources/ --generate-delta --ignore .forceignore
What is the expected result?
The templates sub folder to be included in the component generated from the delta
What is the actual result?
The LWC component folder is generated only with his JS file in it.
Thank you very much
The text was updated successfully, but these errors were encountered: