Runtime storage best practices - Verify First Write Last Requires Additional Info Since Polkadot-v0.9.25

[timurguvenkaya]

Is there an existing issue?

• I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

• This is not a support question.

Content request

Section: https://docs.substrate.io/main-docs/build/runtime-storage/ (Verify First, Update Last)

In substrate polkadot-v0.9.25 branch (https://github.com/paritytech/substrate/tree/polkadot-v0.9.25) #[transactional] macro got deprecated since it is now default behavior (paritytech/substrate#11546 & paritytech/substrate#11431). So now, even if verification happens after storage update, the state won't persist. It will get reverted on Err. Hence, it makes sense to update that section according to new updates. It is still best practice to follow, but it needs updated information.

Are you willing to help with this request?

Yes!

[lisa-parity]

@timurguvenkaya, information about transactional storage added to the documentation:
https://docs.substrate.io/build/runtime-storage/