feat: determine version and type credential in untp playground #260
Conversation
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
Code Coverage Report
|
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.
What type of PR is this? (check all applicable)
Description
Currently, the UNTP playground uses hard-coded mapping within the source code to determine the relationship and versions of different credentials, including extensions like the livestock passport. This approach, where mappings for extensions and their versions are directly added to the code, is considered not scalable. Every time a new beta version is released or a new extension is introduced, the source code would need to be updated, making testing in the playground cumbersome.
To address this scalability issue, a new approach for dynamic version determination is being proposed and discussed. This method relies on examining the context URL found within the verifiable credential. The idea is to use the types of the credentials (present in the "type" array) and the context links to determine the credential type, what it extends (if it's an extension), and the versions of both.
Related Tickets & Documents
Mobile & Desktop Screenshots/Recordings
Added tests?
Added to documentation?
[optional] Are there any post-deployment tasks we need to perform?