Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support the new `metadata.json` format from ink! 3.0.0-rc6
See original GitHub issueI’ve opened an issue against ink! though this is likely just an update needed to py-substrate-interface to support changing metadata.json formats.
If generating ink! metadata for a contract with 3.0.0-rc6, py-substrate-interface will fail to parse types (as it’s a differently formatted file) and other json fields.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Module metadata - Puppet
The metadata.json file is located in the module's main directory, ... the Forge module pages and search function support only the "puppet" value, ......
Read more >Metadata: Support additional JSON formats #767 - GitHub
I am getting the following warning and metadata is not being read. What does PhotoPrism not like? WARN metadata: unknown json in ...
Read more >Rendering the AdChoices icon and overlay | PAL SDK for iOS
Understanding the icon JSON format; Sample Metadata JSON ... an XML ad response, AdChoices is supported only in VAST version 3.0 and above....
Read more >The metadata file (model.json) for Common Data Model
The file-format settings provide metadata related to the data files in the partition. Depending on the type, you may find different fields ...
Read more >What is causing this Invalid JSON ABI structure error?
So when I imported the .contract file like this var contract = fs.readFileSync('./resources/flipper.contract'); const json ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I added initial support for metadata V1 support used in ink!3 in branch https://github.com/polkascan/py-substrate-interface/tree/feature/ink3_support
It’s not thoroughly tested yet (only with simple ‘flipper’ example contract) and depends on an unreleased change of https://github.com/polkascan/py-scale-codec/commit/d80e1c1845ad3c8eec5d1ba7ef8c61a6a138c941, but you can test and monitor progress here.
Yes the PR is released https://pypi.org/project/substrate-interface/1.0.6/, added more unit tests and tested with several contacts, so please let me know if this works for you.