-
-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Markdown support #105
Comments
The text has to be saved in HTML format so that it can be converted to OOXML when generating. Also not everything can be converted to OOXML right now (eg: tables). I don't see the necessity to handle both format when writing. |
Markdown if meant to be transpilled as HTML and markdown renderers can accepts html tags and forwards them so sotring markdown would be backward compatible with vulns storing HTML. Generating the report would be Markdown -> HTML -> OOXML then. So in fact we can keep markdown only while being backward compatible. As most pentesters use markdown, that github issues/comment are using markdown, HackerOne issue are using markdown, etc. having markdown here would facilitate a lot. |
I take this as a "No" then 😆 |
Yes it seems there are some limitations when pasting when going through the tiptap issues. As I find that it's working correctly using HTML and I like the customizability of tiptap I wont change the editor. Feel free to explore tiptap customization capabilities and if you find a way to make it work flawlessly I will gladly add it to the project. |
Even for HTML could you enable the link shortcut on the editor. |
Not yet as it should also be handled in the OOXML conversion. |
I'd love to have this feature too. I (and I am sure many other folks around here) tend to work in Markdown (in either Outline/Notion/Sublime) due to many reasons:
In my scenario, I wouldn't need the pwndoc itself to support markdown editing, but at least it'd be awesome to be able to copy a whole markdown (with all findings/evidence images/etc) and that it parsed all content (provided a specific format, ofc) to directly import to your pwndoc DB and generate a report. Would something like this ("Import Markdown") be easier to implement than rather full markdown support which implies an editor change? |
It would be nice to have alternative Markdown support for findings fields rather than HTML. Using HTML or Markdown could be set up globally in the admin area.
Example of similar tool that has Markdown support: writehat
The text was updated successfully, but these errors were encountered: