search

Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.36k stars 2.78k forks source link

Room - Code block mark down after a space is not applied #49894

Open lanitochka17 opened 4 hours ago

lanitochka17 commented 4 hours ago

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: 9.0.41-2 Reproducible in staging?: Y Reproducible in production?: Y If this was caught during regression testing, add the test name, ID and link from TestRail: N/A Issue reported by: Applause - Internal Team

Action Performed:

  1. Launch app
  2. Open a room chat
  3. Tap header -- room description
  4. Enter and tap save
  5. Tap description
  6. Just add a space after description and tap save
  7. Note code block markdown can be seen
  8. Tap plus icon -- assign task
  9. Enter title
  10. Enter description and tap next
  11. Tap description and add a space and save
  12. Note now code block mark down not applied

Expected Result:

Code block mark down must be applied after a space

Actual Result:

Code block mark down after a space applied in room description but not in task description

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

Screenshots/Videos

Add any screenshot/video evidence

https://github.com/user-attachments/assets/5c68e4b2-7665-4fe2-905d-2f7e9cca6e2f

View all open jobs on GitHub

melvin-bot[bot] commented 4 hours ago

Triggered auto assignment to @abekkala (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

lanitochka17 commented 4 hours ago

@abekkala FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors