remove truncation when convert html to markdown

[nkdengineer]

Fixed Issues

$ Expensify/App#63711

Tests

1. What unit/integration tests cover your change? What autoQA tests cover your change?
2. What tests did you perform that validates your changed worked?

QA

1. What does QA need to do to validate your changes?
2. What areas to they need to test for regressions?

Result

Screen.Recording.2025-07-09.at.21.28.34.mov

[srikarparsi]

Hey @justinpersaud, reassigning you here if that's okay since it deals with this issue

[justinpersaud]

@nkdengineer your proposal mentioned we would

Truncate the final result

Is that no longer necessary?

Also, are there any other tests we should do with regards to pasting now that truncation is being removed?

[nkdengineer]

Truncate the final result

It's just the add-on. Here're the reasons I think we don't need to truncate the final result:

1. User still can enter more than maximum length (10.000)

so if we truncate the final result here, it can cause the inconsistency

2. User can be confused if we truncate the final result without any warnings.

Also, are there any other tests we should do with regards to pasting now that truncation is being removed?

We removed the maxBodyLength in htmlToMarkdown, it's more generic now so I think no test is needed

[justinpersaud]

thanks, the 10k char limit seems good to me

[os-botify]

🚀 Published to npm in 2.0.147 🎉