Fix/special characters link rendering

[gawandeabhishek]

Details

We are resolving the issue where special characters, such as the spade symbol (♤), in comments are being displayed as plain text instead of clickable links on Expensify's staging site.

Fixed Issues

$ #44835
$ PROPOSAL: #44835 (comment)

Tests

1. Verify that special characters like the spade symbol (♤) in comments are now clickable links.

• Verify that no errors appear in the JS console

Offline tests

QA Steps

1. Verify that special characters like the spade symbol (♤) in comments are now clickable links.

• Verify that no errors appear in the JS console

PR Author Checklist

Sure, let's fill out each item based on your proposal:

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above

  • $ [$250] Chat-On adding spade symbol, link is changed to text. #44835
  • PROPOSAL: [$250] Chat-On adding spade symbol, link is changed to text. #44835 (comment)

• I wrote clear testing steps that cover the changes made in this PR

  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e., verify an input displays the correct error message if the entered data is not correct)

• I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e., verify the default avatar icon is displayed if the app is offline)

• I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g., long loading states that impact usability).

• I included screenshots or videos for tests on all platforms

• I ran the tests on all platforms & verified they passed on:

  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop

• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)

• I followed proper code patterns (see Reviewing the code)

  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e., toggleReport and not onIconClick)
  • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g., myBool && <MyComponent />.
  • I verified that comments were added to code that is not self-explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy/text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-English text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates, and phone numbers shown in the product are using the localization methods
  • I verified any copy/text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from Figma or has been approved by marketing (to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed

• If a new code pattern is added, I verified it was agreed to be used by multiple Expensify engineers

• I followed the guidelines as stated in the Review Guidelines

• I tested other components that can be impacted by my changes (i.e., if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)

• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)

• I verified any variables that can be defined as constants (i.e., in CONST.js or at the top of the file that uses the constant) are defined as such

• I verified that if a function's arguments changed that all usages have also been updated correctly

• If any new file was added, I verified that:

  • The file has a description of what it does and/or why it is needed at the top of the file if the code is not self-explanatory

• If a new CSS style is added, I verified that:

  • A similar style doesn't already exist in the codebase to avoid redundancy

Let me know if there are any specific points you need more details or further clarification on!

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[gawandeabhishek]

I have read the CLA Document and I hereby sign the CLA