UCO Issue 640: Link core:informalType as parent of type-describing properties (for CASE 2.0.0)#171
Merged
Merged
Conversation
…operties Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
References: * #167 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Issue 167: Adjust top Makefile dependency ordering in submodule initialization
No effects were observed on Make-managed files. References: * ucoProject/UCO#640 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
UCO Issue 640: Link `core:informalType` as parent of type-describing properties
No effects were observed on Make-managed files. References: * ucoProject/UCO#640 Signed-off-by: Alex Nelson <alexander.nelson@nist.gov>
Closed
16 tasks
Member
Author
|
This PR is ready for review and merge. |
plbt5
approved these changes
Feb 14, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR does not require committee processing for merging. It should pass CI and receive an approving review, though.
This PR is part of implementing UCO Issue 640 in CASE, bringing forward changes to CASE 2.0.0. New features were only new to CASE 1.4.0; no further change occurs for CASE 2.0.0 aside from catch-up merging.