Include equivalent Text component

[southkeys]

Thanks for this great lib.

Since this lib parses and renders markdown already in TextInput, it should just provide Text component that renders it.

Not only that but you have the ExpensiMark vs CommonMark discrepancy which requires digging into the source code to ensure you don't have inconsistencies with rendering lib

Without digging into source code, can someone list out the differences between ExpensiMark and CommonMark?

[southkeys]

looks like it's been in the works for ... 9 months?

#125

[RalissonMattias]

Any news?

[tomekzaw]

https://x.com/tomekzaw_/status/1834888525080101118

[erickriva]

@tomekzaw any news about it? Something we can help?

[tomekzaw]

No update on this, unfortunately. First we need to improve the logic of MarkdownTextInput in native code and then we use the same solution for MarkdownText hopefully.