Have optional type guard for persist middleware

[ProgMiner]

Hello!

Why haven't any option that to provide an ability to check stored state while hydration?
As I see, the current implementation don't provide any verification options but only non-intrusive observers for hydration.
It seems strange that we just trust data in storage that can be directly changed by user...
Are there reasons to not adding an ability to verify data well-formedness just right after parsing and before merging?
I think it could be implemented as an optional parameter for createJSONStorage since it imposes a naive case from any to StorageValue<S> after parsing

[dai-shi]

createJSONStorage is unsafe by design. You should provide a safe storage in that case without using createJSONStorage.
I think we should be more explicit about it in our docs. @dbritto-dev

[ProgMiner]

Thank you for answering!
But why not add a safe variant of createJSONStorage?

[dai-shi]

Because there are so many options around validation. I think it could be a third-party library.