You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A GetState interface would allow us to hide the Store type when using it in situations that shouldn't have access to the Store methods.
This is relevant for cases where you don't want the consumer to be able to do operations on the Store. e.g. redux-observable where the Epic should not have access to the Store because that would allow the Epic to dispatch actions manually, which would be an error.
It would probably look something like:
interfaceGetState<S> {
SgetState();
}
The Store<S> would implement the GetState interface.
The text was updated successfully, but these errors were encountered:
A GetState interface would allow us to hide the
Store
type when using it in situations that shouldn't have access to theStore
methods.This is relevant for cases where you don't want the consumer to be able to do operations on the
Store
. e.g.redux-observable
where theEpic
should not have access to theStore
because that would allow theEpic
to dispatch actions manually, which would be an error.It would probably look something like:
The
Store<S>
would implement theGetState
interface.The text was updated successfully, but these errors were encountered: