Currently, the setFooStore config method will also attempt to restore a session and possibly contact AuthN to refresh. With v0.9.0 it returns a promise that a host app can use to trigger business logic.
This makes the mixture of configuration and side effects awkward, and also introduces an order-of-operations problem where setHost must be configured before setFooStore can operate reliably.
Solution: extract restoreSession() into an explicit public method.
Currently, the
setFooStoreconfig method will also attempt to restore a session and possibly contact AuthN to refresh. With v0.9.0 it returns a promise that a host app can use to trigger business logic.This makes the mixture of configuration and side effects awkward, and also introduces an order-of-operations problem where
setHostmust be configured beforesetFooStorecan operate reliably.Solution: extract
restoreSession()into an explicit public method.