We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Would there be value in establishing a constant in each types file for the oscal version IE
const OSCAL_VERSION = "x.x.x"
with some function for getting/setting that version for use in a defined object?
Use case would be coupling this version with its intended types as downstream consumers look to handle multiple versions.
Need to add functionality to the generate process that adds functions and derives the version of oscal from the schema.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Would there be value in establishing a constant in each types file for the oscal version IE
with some function for getting/setting that version for use in a defined object?
Use case would be coupling this version with its intended types as downstream consumers look to handle multiple versions.
Implications
Need to add functionality to the generate process that adds functions and derives the version of oscal from the schema.
The text was updated successfully, but these errors were encountered: