Closed larry0x closed 1 year ago
Would love to know your thoughts on this design decision @shanev @jhernandezb @0xekez
i'm pro. will need to update a couple contracts if we land this, but that's fine. forward!
@JakeHartnell do you know why CI doesn't run?
In the new version does ExecuteMsg
still need <T>
?
enum ExecuteMsg {
Mint {
token_id: String,
owner: String,
token_uri: Option<String>,
extension: T,
},
}
In the new version does
ExecuteMsg
still need<T>
?enum ExecuteMsg { Mint { token_id: String, owner: String, token_uri: Option<String>, extension: T, }, }
T
is for the extension data, for example cw-metadata-onchain puts the metadata in the extension.
Not sure what's up with CI, but ran all checks locally, and we should be good. Thanks for this @larry0x!
Current:
New:
This is backward compatible because
ExecuteMsg
serializes to the same JSON.