Skip to content
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

Ability to extract sourcecode #27

Open
ajeanmahoney opened this issue Jan 8, 2024 · 0 comments
Open

Ability to extract sourcecode #27

ajeanmahoney opened this issue Jan 8, 2024 · 0 comments
Assignees

Comments

@ajeanmahoney
Copy link
Collaborator

ajeanmahoney commented Jan 8, 2024

The RPC extracts the following code components in order to validate them before publication: ABNF, YANG modules, MIBs, and XML. Other code components may be validated in the future.

The user should be able to extract code tagged with <sourcecode> and save it out as a separate file. If a filename is not provided by the the name attribute, then the XML's filename can be used (e.g., draftstring-NN or rfcNNNN) plus the sourcecode extension (e.g., rfcNNNN.abnf). Note that YANG modules usually have dates in their names (e.g., [email protected]), but their filenames are usually provided in the sourcecode. If there multiple code components, then they can be named rfcNNNNa.abnf, rfcNNNNb.abnf, etc).

It should be possible to select just one sourcecode type (e.g., "Extract YANG module" in addition to "Extract all code components")

The ability to extract sourcecode is currently provided by the following scripts

  • extractyang, which is run on the text output to extract YANG
  • rfclint, which is run on the RFCXML file to extract ABNF and XML
  • bwstrip, which is run on the text output to extract an SNMP MIB
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants