- 
                Notifications
    You must be signed in to change notification settings 
- Fork 2.7k
          TryDecodeEntireState check for storage types and pallets
          #13013
        
      base: master
Are you sure you want to change the base?
Conversation
| I think 1. is a good start. It is opt-in and easy to use 👍 | 
| Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions. | 
| Don't you dare bot. | 
| This PR is mostly done, as is up for grabs if anyone wants to push it to completion. | 
| Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions. | 
| Hey, is anyone still working on this? Due to the inactivity this issue has been automatically marked as stale. It will be closed if no further activity occurs. Thank you for your contributions. | 
| bot rebase | 
| Rebased | 
| The CI pipeline was cancelled due to failure one of the required jobs. | 
closes paritytech/polkadot-sdk#241
Add infrastructure needed to have a
Pallet::decode_entire_state(), which makes sure all "typed" storage items defined in the pallet are decode-able.This is not enforced in any way at the moment. Teams who wish to integrate/use this in the
try-runtimefeature flag should addframe_support::storage::migration::EnsureStateDecodesas the LAST ITEM of the runtime's custom migrations, and pass it toframe-executive. This will make it usable intry-runtime on-runtime-upgrade.try-runtime-cliin a few places. Namely, we probably want this somehow integrated infollow-chainandfast-forward.