-
Notifications
You must be signed in to change notification settings - Fork 78
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
force:source:status command incorrectly identifying modified profiles containing parentheses #2212
Comments
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. |
reproduced this... my initial thought is that the encoded
continued to confirm this %28 theory by creating a custom metadata object
continue to pull/status and see it always as |
This issue has been linked to a new work item: W-13593791 |
This is fixed in the latest CLI releases |
When the profile name includes parentheses, for example, My(awesome)profile, the sfdx force:source:status command always treats the profile as if it has been modified.
When the profile is pulled using the sfdx force:source:pull command, the profile is escaped and stored at the following path:
force-app/main/default/profiles/My%28awesome%29profile.profile-meta.xml
Even if the sfdx force:source:status is run again, the CLI still considers the profile as added to the remote repository.
The text was updated successfully, but these errors were encountered: