Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document metadata format #940

Open
cmichi opened this issue Sep 23, 2021 · 2 comments
Open

Document metadata format #940

cmichi opened this issue Sep 23, 2021 · 2 comments
Assignees
Labels
A-ink_metadata [ink_metadata] Work item

Comments

@cmichi
Copy link
Collaborator

cmichi commented Sep 23, 2021

We should document the metadata format for a stable 3.0 release. Without documentation the hurdle to build third party tools (like different UI's or CLI tools) is too high.

Ideally the ink-docs would contain a section on the metadata as well, maybe linking to more extensive documentation in the ink_metadata crate?

Once we have this documentation we should also communicate it to stakeholders (Patract, etc.).

@cmichi cmichi added the A-ink_metadata [ink_metadata] Work item label Sep 23, 2021
@yjhmelody
Copy link
Contributor

yjhmelody commented Oct 12, 2021

@Robbepop Hi, I found polkadot apps started to use new metadata format(My metadata cannot be uploaded to apps).

PortableRegistry: 3: Error extracting {"path":[],"params":[],"def":{"composite":{"fields":[{"name":"inner","type":2,"typeName":"FixedArray32<u8>","docs":[]}]}},"docs":[]}: Cannot read properties of undefined (reading 'toString')

What's the changes ?
I thought it was just changing the index from 1 to 0, but it doesn’t seem to be.

@cmichi
Copy link
Collaborator Author

cmichi commented Dec 10, 2021

@ascjones I just merged #923, polkadot-js/api has been updated in polkadot-js/api#4289. So this issue is no longer blocked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-ink_metadata [ink_metadata] Work item
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants