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

Fix single backtick code block is rendered within a triple backtick code block when followed by an emoji #806

Conversation

ra-md
Copy link
Contributor

@ra-md ra-md commented Sep 26, 2024

Fixed Issues

$ Expensify/App#49276

Tests

  1. What unit/integration tests cover your change? What autoQA tests cover your change?
    Updated the unit test to cover an inline code block followed by an emoji within a triple backtick code block.
  2. What tests did you perform that validates your changed worked?

Update the related regex in the node_modules/expensify-common/dist/ExpensiMark.js and send this in the Expensify composer.

```
`diamond` 💍
```

Verify that the single backtick code block is not rendered within the triple backtick code block.

`diamond` 💍

QA

  1. What does QA need to do to validate your changes?
    Same as test above
  2. What areas to they need to test for regressions?
    Tests related to inline code inside code fences.

@ra-md ra-md requested a review from a team as a code owner September 26, 2024 05:32
Copy link

github-actions bot commented Sep 26, 2024

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

@melvin-bot melvin-bot bot requested review from carlosmiceli and removed request for a team September 26, 2024 05:32
@ra-md
Copy link
Contributor Author

ra-md commented Sep 26, 2024

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

@carlosmiceli carlosmiceli merged commit 1ab0b58 into Expensify:main Sep 27, 2024
6 checks passed
Copy link

🚀Published to npm in v2.0.94

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants