Skip to content

Implemented a command catalog exporting as a json#6597

Open
moste00 wants to merge 2 commits into
rizinorg:devfrom
moste00:feature/command_catalog_json
Open

Implemented a command catalog exporting as a json#6597
moste00 wants to merge 2 commits into
rizinorg:devfrom
moste00:feature/command_catalog_json

Conversation

@moste00

@moste00 moste00 commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

Your checklist for this pull request

  • I've read the guidelines for contributing to this repository.
  • I made sure to follow the project's coding style.
  • I've documented every RZ_API function and struct this PR changes.
  • I've added tests that prove my changes are effective (required for changes to RZ_API).
  • I've updated the Rizin book with the relevant information (if needed).
  • I've used AI tools to generate fully or partially these code changes and I'm sure the changes are not copyrighted by somebody else.

Detailed description

This implements suggestion C1 of #6543, namely, it exports the full-command tree as a json tree. The export can be triggered by both a command line option --cmd-catalog json, and via an internal help statement like ?*, named ?+j.

Test plan

For now, none. I plan to add it soon. The following will be implemented:

(1) A test that asserts the top-level number of children is the same as the number of commands outputed by ?

(2) Manual comparison of the output against the yaml description of the commands, by both humans and several LLMs

Closing issues

None, small part of addressing #6543.

@moste00 moste00 force-pushed the feature/command_catalog_json branch from 4e1c596 to 68ef072 Compare July 11, 2026 22:22
@moste00

moste00 commented Jul 11, 2026

Copy link
Copy Markdown
Contributor Author

@notxvilka please review ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant