Added custom flags support #15
Open
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
tomadimitrie
force-pushed
the
custom-flags
branch
2 times, most recently
from
0c3497b
to
1071d81
Compare
tomadimitrie
force-pushed
the
custom-flags
branch
from
1071d81
to
d4c357a
Compare
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.
Currently, the class uses hardcoded flags for the methods:
get(USER_PRESENT,ATTESTED_CREDENTIAL_DATA_INCLUDED)update(USER_PRESENT)However, some relying parties need certain flags. The most useful example is
USER_VERIFIED.This PR introduces the option to specify the flags, without breaking current behavior. It also includes some tests for this feature.