-
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
SF V2 - some HTML entities being incorrectly escaped during push #2448
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. |
Hello @rhobkirkcertinia 👋 It looks like you didn't include the full Salesforce CLI version information in your issue. A few more things to check:
Thank you! |
This issue has been linked to a new work item: W-14079220 |
found it, got a fix PR ready. |
Brilliant, thanks @mshanemc! |
@rhobkirkcertinia can you try this with your codebase using |
welp, that turned out really bad (caused a regression with the parsing of some other html entities). #2455 gonna roll that back and come up with some other opton. |
Ouch, thanks for trying @mshanemc . I'll hang fire testing until there is a new solution - please can you re-open this issue in the mean time? |
this issue stayed open, only the PR associated was closed |
OK, after a much better investigation than the first time, here's what I've found. sfdx < 7.184Local project since then (sfdx >= 7.184 and sf >=2 )CLI was escaping the ampersand character I think I can fix that safely. It'll still clobber labels down to a |
Thanks @mshanemc 👍 |
Fixed in the latest version of |
Summary
In our
customlabels
we have some HTML entities that get pushed up to the org.These are things like
<
,>
and 
etc. All of these seem to work except 
which gets encoded when pushing to the org and ends up rendering as the literal character code when used. 
is a non-breaking space and is the same as using
. We've tried switching over to that and it also got encoded and therefore didn’t work either. This appears to be a regression as SFDX cli version 7.183.1 doesn’t have this issue.This issue might exist with other characters too - this is the only one that we've spotted so far.
Steps To Reproduce
3 results, and 1 other
3 results, and 1 other
Expected result
HTML entities are not escaped so that they are rendered as expected (and per previous CLI behaviour)
Actual result
HTML entities are escaped, causing them to be rendered as the string literal version of the character
System Information
@salesforce/cli/2.5.8 darwin-arm64 node-v18.15.0
The text was updated successfully, but these errors were encountered: