Alexander Theißen
Alexander Theißen
> To allow a smooth transition for developers and avoid a sudden breaking change in the ecosystem, the Metadata trait is extended with a metadata_v15. The Metadata_metadata runtime function will...
> New runtime call needs adding for each metadata bump (is this annoying to do?) It is. Because every runtime needs to implement them. While with a general API they...
I don't get why you are so keen on encoding the version in the name of the runtime API. Can you explain? This will me a massive headache because the...
I agree we should not use `Option` for `version_at()`. I propose the following API: ```rust fn metadata_at_version(version: u32) -> Option; fn metadata_versions() -> Vec; ``` The original metadata version function...
> > Or more specifically; should the metadata include information about older versions of calls? > > No. Each runtime always only supports one version of the runtime function. The...
> To the node side, yes. But on the runtime side you only have one. For the node side this is important to be able to call the old version...
> I guess I had in mind that, like the chainHead_unstable_x rpc methods, the V15 metadata could by default be available in live nodes (but not "exposed" via the version...
Don't forget to run `cargo +nightly fmt`
bot bench -v PIPELINE_SCRIPTS_REF=bm-fallback $ pallet dev pallet_contracts