-
Notifications
You must be signed in to change notification settings - Fork 23
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
feat(oscal)!: oscalmodel interface implementation for component definitions #874
Merged
meganwolf0
merged 11 commits into
main
from
747-oscalmodel-interface-implementation-for-component-definitions
Jan 17, 2025
Merged
feat(oscal)!: oscalmodel interface implementation for component definitions #874
meganwolf0
merged 11 commits into
main
from
747-oscalmodel-interface-implementation-for-component-definitions
Jan 17, 2025
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
meganwolf0
changed the title
747 oscalmodel interface implementation for component definitions
feat!(oscal): OSCALModel interface implementation for component definitions
Jan 13, 2025
meganwolf0
changed the title
feat!(oscal): OSCALModel interface implementation for component definitions
feat(oscal)!: OSCALModel interface implementation for component definitions
Jan 13, 2025
meganwolf0
changed the title
feat(oscal)!: OSCALModel interface implementation for component definitions
feat(oscal)!: osaclmodel interface implementation for component definitions
Jan 14, 2025
meganwolf0
changed the title
feat(oscal)!: osaclmodel interface implementation for component definitions
feat(oscal)!: oscalmodel interface implementation for component definitions
Jan 14, 2025
…component-definitions
mildwonkey
previously approved these changes
Jan 16, 2025
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'm sorry, I thought I submitted this yesterday!
I left some non-blocking nitpicks - you're free to ignore them (or address in a later PR, I know you have a few queued up)
brandtkeller
previously approved these changes
Jan 16, 2025
…ace-implementation-for-component-definitions
meganwolf0
dismissed stale reviews from brandtkeller and mildwonkey
via
January 16, 2025 17:12
11a5e46
…component-definitions
…component-definitions
mildwonkey
approved these changes
Jan 17, 2025
meganwolf0
deleted the
747-oscalmodel-interface-implementation-for-component-definitions
branch
January 17, 2025 19:14
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Implementation of the OSCALModel interface for a Component Definition. Additionally:
generate
complete-schema
HandleExisting
function as an error was noted with variable overwriting (+ added test)Note Skipping function updates to compose/validate to use this interface. As those are probably wrapped more directly in the validation refactor, opting to defer updates to those issues.
Related Issue
Fixes #747
Type of change
Checklist before merging