Open omarhurani opened 8 months ago
Thanks for asking, it certainly helps!
I had some drafts towards this, but took them out to accelerate #172 over the line... Realistically I think getting it implemented would still need quite a bit of work.
The biggest challenge I saw with Markdown is tables:
I'm sure there are libraries out there in the NPM ecosystem that could make this easier for us than building from scratch, but today TRP.js supports usage via simple HTML <script>
tags (via IIFE), for the sake of custom human review task UIs in SageMaker Ground Truth and Augmented AI. In those contexts there's no one/obvious module management system - so as far as I understand, taking on dependencies would mean either enforcing some assumptions, or bundling dependencies into the TRP.js IIFE itself and figuring out what we'd need to do to ensure the bundled packages' IP was respected 😖
So the result/tldr is:
.markdown()
for which could help inform the trade-offs, it'd be super useful to hear. For e.g:
---------
s would be best)
Any updates on this? Currently stuck due to the lack of this feature. Might end up having a python script run in the background just for this feature but not ideal.
More interested in this for the tables specifically
Is markdown support
doc.markdown()
planned to come any time soon?