-
Notifications
You must be signed in to change notification settings - Fork 89
Automated generation of handlers documentation #1173
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
Conversation
a2c000f
to
fe7f288
Compare
Looks good to me! I think we can merge this and make some adjustments once I create a proper page in the docs. |
I'd just wait for @e3krisztian approval too, then we merge :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should revise the handler names for some formats to make the handler table more informative to people not knowing the formats by heart, it could be however in another PR.
Please take a look into why LZ4 is appearing 3 times - that looks strange/wrong.
e9eeac9
to
09310c6
Compare
We had to use --unsafe in check-yaml so that it checks syntax but does not attempt to load the YAML itself. Otherwise an error gets triggered by the emoji plugin of mkdocs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the fixes and the patience.
Looks good now! :)
Early draft for handler documentation.
It introduces a
HandlerDoc
class that bothHandler
andDirectoryHandler
requires under theDOC
field. This class takes a name, a handler type, a description, and a list of references.This is both useful for maintainers since the handlers will contain detailed information and references within the code (kinda like module info in Metasploit), and users as this is ultimately used to dynamically generate the documentation available on unblob.org
This is a very early draft. All the DOC fields were generated by copilot and must be reviewed. The markdown structure and what we do with the DOC content is still open to discussion.