Closed tomusdrw closed 3 years ago
Sadly the JSON as presented really helps close to 0.
Address -> AccountId
is in there)So working from that is an impossible task.
So working from that is an impossible task.
Let me know how we can make it possible then. From what I've understood marking types that come from pallet-bridge-messages
would help, is that correct? What format would suit you best regarding the definition of the types?
If that helps we also have networks with these pallets already deployed, namely: wss://wss.rialto.brucke.link
and wss://wss.millau.brucke.link
.
Networks are the best - from there can actually categorize the types into the relevant pallets. (It is the only way this can be managed properly - JSON is great for quick-and dirty, but not for maintaining)
Here is a minimal JSON I came up with after testing with Rococo-local
. Please let me know if that's sufficient. Also feel free to test with live networks mentioned earlier (I'd suggest Rialto cause it has closest type definition to Rococo):
If that helps we also have networks with these pallets already deployed, namely: wss://wss.rialto.brucke.link and wss://wss.millau.brucke.link.
Thank you.
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.
We're planning to deploy Bridge messaging to Rococo/Wococo soonish (PR has been merged).
After the runtime upgrade I suspect there will be a bunch of missing types. You can find all the custom types we currently expect to be needed for Rococo here.
This issue is just a heads up to avoid the API breaking before the upgrade. The types that will be needed are the ones from
pallet-bridge-messages
(I think it may end up adding almost all of the types from the linked JSON file).