Implement custom data contract names #153
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
pshenmic
added
indexer
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
pshenmic
force-pushed
the
feat/data-contract-names
branch
from
d182fe6 to
e6ab600
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.
Issue
Indexer side implementation of the of the #138 task.
It is now possible to verify your data contract and set custom name for your data contract on the Platform Explorer. To do that, you have to publish a document to the data contact with identifier
8AoJWLcT4t1uFuWkeTfbeN2EuGuvX2nJsZMVpDsF4ASmwith your desired name from the identity you used to deploy your contract with.Things done
namefield to the frontend