[stable2412] Backport #7028#7067
Conversation
#7028) Currently `(A, B, C)` and `((A, B), C)` change the order of implications in the transaction extension pipeline. This order is not accessible in the metadata, because the metadata is just a vector of transaction extension, the nested structure is not visible. This PR make the implementation for tuple of `TransactionExtension` better for tuple of tuple. `(A, B, C)` and `((A, B), C)` don't change the implication for the validation A. This is a breaking change but only when using the trait `TransactionExtension` the code implementing the trait is not breaking (surprising rust behavior but fine). --------- Co-authored-by: command-bot <> Co-authored-by: Bastian Köcher <git@kchr.de> (cherry picked from commit b5a5ac4)
|
This pull request is amending an existing release. Please proceed with extreme caution,
Emergency Bypass
If you really need to bypass this check: add |
|
This backport is controversial, it is a breaking change both in rust code and in the runtime behavior in general.
|
acatangiu
left a comment
There was a problem hiding this comment.
Should be fine for 2412
georgepisaltu
left a comment
There was a problem hiding this comment.
As discussed, I think this change should make it into the release ASAP, especially because the feature is so new, which should mean we don't break anyone actually.
|
cc @paritytech/release-engineering |
Backport #7028 into
stable2412from gui1117.See the documentation on how to use this bot.