Disambiguate identifier versus CASE website #144
Merged
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
The duplicated UUID was found while reviewing CASE-Examples-QC PR 54. From the linked `MobileAccountFacet`s, the `MobileAccount` node on the CASE website does not appear to characterize the same thing. A follow-on patch will regenerate Make-managed files. References: * ajnelson-nist/CASE-Examples-QC#54 Signed-off-by: Alex Nelson <[email protected]>
References: * ajnelson-nist/CASE-Examples-QC#54 Signed-off-by: Alex Nelson <[email protected]>
|
I checked the other UUIDs updated in CASE website PR 294 and didn't find occurrences of them in or since the merge-state before PR 143. I think the shared UUIDs are removed once this PR is merged. |
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.
This is part of implementing CASE-Examples-QC PR 54.