-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
[$1000] Web - The ampersand (&) is not displaying properly in the NewDot under the category selector #34735
Comments
Triggered auto assignment to @NicMendonca ( |
This is reproducible with our NewDot testing policy with the categories that come from NetSuite. |
Job added to Upwork: https://www.upwork.com/jobs/~01fd5614918bf77eaf |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @situchan ( |
one of my clients project had the same bug ( in a blogging website), the problem was with encoding/decoding of contents. |
📣 @AliSinaYOusofi! 📣
|
Contributor details |
|
No proposals yet |
📣 It's been a week! Do we have any satisfactory proposals yet? Do we need to adjust the bounty for this issue? 💸 |
@NicMendonca, @situchan Huh... This is 4 days overdue. Who can take care of this? |
Upwork job price has been updated to $1000 |
ProposalPlease re-state the problem that we are trying to solve in this issue.The ampersand (&) is not displaying properly in the NewDot under the category selector What is the root cause of that problem?The BE is returning html encoded categories. What changes do you think we should make in order to solve the problem?We need to App/src/libs/OptionsListUtils.ts Lines 913 to 914 in a44e804
We have done a similar thing to tags to remove unnecessary escaping keys should do similar here What alternative solutions did you explore? (Optional)If we don't want to change what we return to the BE then we can only unescape before displaying it only same as what we did for tag |
@MonilBhavsar yea this bug is already fixed. do nothing? |
@rushatgabhane this is not "do nothing" issue. Please check https://expensify.slack.com/archives/C049HHMV9SM/p1705434349164419 |
ah thanks! looks like it's a backend bug then |
Yes, some users are still experiencing this bug |
I don't think this should be considered as a BE issue. This is issue is similar to #30734 which is But rather this issue is caused by ND not auto html-decoding as we do in OD. Now if u enter |
Current assignee @situchan is eligible for the Internal assigner, not assigning anyone new. |
Made this internal while I figure the root cause |
Trying to reproduce locally |
@MonilBhavsar @muttmuure @situchan this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks! |
Discussing it here https://expensify.slack.com/archives/C03TQ48KC/p1707467669800489 |
@MonilBhavsar, @muttmuure, @situchan Uh oh! This issue is overdue by 2 days. Don't forget to update your issues! |
@MonilBhavsar @cead22's comment is here:
Are all of your questions answered? |
Yes answered. I think we all agree that we do nothing for categories added in oldDot but take necessary steps for categories added in newDot. So I am going to create a new issue for wave8 - simplified collect to ensure categories added from newDot are always decoded across all layers of the app. |
Closing in favor of #36473 |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 1.4.27-0
Reproducible in staging?:
Reproducible in production?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @puneetlath
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1705434349164419
Action Performed:
Expected Result:
The ampersand (&) is displaying properly in the NewDot under the category selector
Actual Result:
The ampersand (&) is not displaying properly in the NewDot under the category selector
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Add any screenshot/video evidence
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: