Derive TypeInfo impls for meta type definitions #21
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
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.
#19 enables scale encoding of the
scale-infotype definitions. In order to decode these from Rust, a client can add a dependency to thescale-infocrate.However, other languages will need to define their own types which will need to be handwritten. e.g. https://github.com/polkadot-js/api/blob/a67ffce84736e12216721d7191aadba47d9944f8/packages/types/src/interfaces/contractsAbi/definitions.ts#L76.
This PR adds a
dogfoodfeature (may be renamed) which will generateTypeInfoimplementations for thescale_info::Typetypes themselves. This will enable generating equivalent types in other languages which can be used for decoding.Depends on #20.