You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When uploading a form to kobocollect any markdown in the question is automatically converted to HTML in the final output. It would be nice if this could parsed within our system also
Describe the solution you'd like
Likely the best option would be to first convert the markdown to HTML within the backend docker API, so that when the output is received it is still just HTML. If not possible to get working it could be possibly to
Hi @chrismclarke, Thanks for this issue and such a clear description, I did some digging and the enketo-transformer
library was already handling this issue, we had just disabled the feature, and I have pushed a fix for it on the docker API PR , Please check this out and let me know if it's conclusive
Is your feature request related to a problem? Please describe.
When uploading a form to kobocollect any markdown in the question is automatically converted to HTML in the final output. It would be nice if this could parsed within our system also
Describe the solution you'd like
Likely the best option would be to first convert the markdown to HTML within the backend docker API, so that when the output is received it is still just HTML. If not possible to get working it could be possibly to
Additional context
There's a lot of packages that can handle markdown-html conversion. I can't remember if the API uses javascript or python, for JS there's a few listed at:
https://npmtrends.com/markdown-it-vs-marked-vs-remarkable-vs-showdown
I've used marked in the past and worked well but open to any. There are also likely multiple for python.
Example of form with markdown that does not render markdown in table headings:
https://dashboard.picsa.app/monitoring/79d4cc31-96bf-4ea6-b639-f7d09580a561
Original xlsx:
aABxJMaJqbqQjrCF6t9tkG.xlsx
The text was updated successfully, but these errors were encountered: