shared/cred: Allow absent subject #343
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 loop expression removes the assurances on the order, but the processor already does not enforce full deterministic encoding.
A new case is added for the 'something unexpected' category that would otherwise be empty now.
|
Thanks, looks good to me. |
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.
#341 had an easy follow-up -- was there ever a reason to require a CCS to have a subject, other than that it is there in the examples?
With this, I think that the parser can deal with all the credentials which I've previously created manually.
The loop expression removes the assurances on the order, but the processor already does not enforce full deterministic encoding.