Split credential serializer into two #718
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
Signed-off-by: wadeking98 <wkingnumber2@gmail.com>
amanji
reviewed
Dec 8, 2021
amanji
approved these changes
Dec 8, 2021
amanji
changed the title
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.
Moved v4 CredentialTypeSerializer into CredentialTypeSchemaSerializer and CredentialTypeExtandedSerializer.
CredentialTypeSchemaSerializeronly contains the information needed to be displayed on the/api/v4/schemasendpoint whileCredentialTypeExtandedSerializercontains the issuer, highlighted attributes, etc. This allows us to limit the amount of unneeded information displayed at the schemas endpoint while still preserving the new orgbook functionality.Signed-off-by: wadeking98 wkingnumber2@gmail.com