Skip to content
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

Retrieve changes js-meta file extensions #871

Closed
dvon88 opened this issue Feb 24, 2021 · 4 comments
Closed

Retrieve changes js-meta file extensions #871

dvon88 opened this issue Feb 24, 2021 · 4 comments
Labels
investigating We're actively investigating this issue plugin-source should be tested against new source plugin

Comments

@dvon88
Copy link

dvon88 commented Feb 24, 2021

Summary

Sometime when retrieving from an org, the js-meta.xml files are changed to css-meta.xml This only happens with LWC that has a CSS file, but does not always occur with all files. However, once it occurs with one file, it always occurs with that file. The component then cannot be deployed to an org unless the file is manually renamed to js-meta.xml again.

Steps To Reproduce:

  1. Retrieve LWC
  2. Check their extensions.

Expected result

Retrieve all files as normal.

Actual result

Some components jss-metal.xml files are changed to css-meta.xmls

SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
sfdx-cli/7.85.1-2fb9e41053 linux-x64 node-v12.18.3

SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.1 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.9.5 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-diff 0.0.6
@salesforce/sfdx-trust 3.6.0 (core)
alias 1.1.5 (core)
analytics 1.12.1 (core)
auth 1.4.6 (core)
config 1.2.3 (core)
generator 1.1.3 (core)
salesforcedx 50.15.0 (core)
├─ limits 1.0.3 (core)
├─ user 1.0.9 (core)
├─ schema 1.0.3 (core)
├─ templates 50.4.0 (core)
├─ apex 0.1.4 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7 (core)
├─ custom-metadata 1.0.11 (core)
└─ salesforce-alm 50.15.0 (core)
sfdx-cli 7.85.1 (core)

OS and version:
Ubuntu 20.04

@dvon88 dvon88 added the investigating We're actively investigating this issue label Feb 24, 2021
@github-actions
Copy link

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

@jsmithdev
Copy link

Has happened to me as well. I'm using Ubuntu 20.10 atm.

@mshanemc mshanemc added the plugin-source should be tested against new source plugin label May 20, 2021
@github-actions
Copy link

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

@github-actions
Copy link

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigating We're actively investigating this issue plugin-source should be tested against new source plugin
Projects
None yet
Development

No branches or pull requests

4 participants