Add MarkdownText component for preview

[tomekzaw]

Work in progress. Closes #93.

[nandorojo]

Can't wait for this!

Will it also have web support?

[tomekzaw]

Yes, it will support web, in fact this is the easiest part here 😄

[nandorojo]

Can’t wait for it to get released 🙏

[pzatorski]

This is great! 🚀 @tomekzaw are there any blockers for shipping this?

[nandorojo]

If I were to guess, it would be Android and Web support, as the PR appears to only have ios code for now.

@tomekzaw should I try to add web support here to help push things forward?

[tomekzaw]

@pzatorski Thanks! First we need to address some issues related to MarkdownTextInput component, especially for web. Once completed, we will return to this draft PR.

@nandorojo Implementing web version of MarkdownText component is the cherry on top; I'm afraid that adding it now won't make things much faster for us. Anyway, if you'd like to give it a shot then feel free to go ahead, I won't stop you 😉

[peter-olom]

Hi, any progress with this?

[arasrezaei]

Can't wait!

[arasrezaei]

When will be available?

[sergeymild]

When will be available?

[SuperBesse]

Any news ?

[southkeys]

what are you guys using for rendering ?

[csulit]

Any news?

[Gautammer]

what are you guys using for rendering ?

[bbaoNg97]

Hi, any update on this?

[tomekzaw]

Hi, we'd like to first merge #520 and then use an analogous approach in this PR.

[markwitt1]

Is it performant enough to just use it as a disabled input component?

[tomekzaw]

@markwitt1 Yes, but there are some layout-related differences between Text and TextInput. If you're fine with those, you can just use a disabled TextInput solely for Markdown rendering.

[ice-cap0]

how about in a list? any perf considerations?

[ericpoulinnz]

@tomekzaw any updates on this PR / #520 ? Will be good to know to factor in which library we are using.

I guess using a disabled TextInput input could work, although we will also need it in a list, so I guess I would also want to know the answer to the above about performance in a list

[tomekzaw]

@ericpoulinnz There are no updates on this PR. As for #520, I'm currently working on adapting it to RN 0.79.1+.

When it comes to using a disabled MarkdownTextInput inside a list, probably no one tried it before so we don't have any idea about its performance, but hopefully this should be quite straightforward for you to measure.

[ericpoulinnz]

Thanks for the quick response @tomekzaw .

The performance was not too bad from my quick tests, but ran into the (obvious in hindsight) issue that links are not clickable in the TextInput mode (as far as I can see?)

So I will use another solution for the meantime but eagerly await this PR being merged in :)

[arpitv96171]

@tomekzaw Hi

When will we be able to see this component, especially since #520 is now merged? Eagerly waiting for this one.

[tomekzaw]

@arpitv96171 Hi, we still haven't rolled out #520 to production so we need to focus on this first. Once it's working in the Expensify/App hopefully we should have some time to work on the MarkdownText component.

[tomekzaw]

Hi all, please check out react-native-enriched-markdown library which exposes EnrichedMarkdownText component.