[Session] Extract resumeSession out #3811
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
resumeSession
is a thin wrapper overinitSession
which setssetIsInitialLoad(false)
to hide the splash and then becomes effectively the same asinitSession
. I was wondering if I could get rid of it, and the only usage ofresumeSession
was from top-levelInnerApp
components which, conveniently, were the ones who neededisInitialLoad
in the first place (to hide the splash). So I removedresumeSession
from the Session API and removedisInitialLoad
from its context.Why?
I want to pare it down, and
resumeSession
doesn't depend on any knowledge that isn't already available through the Session API. So it made sense to me to move it out to keep that code more focused. Conceptually we have one instance of theInnerApp
component (it's just forked between two platforms). The local usage also makes sense because it lets us get rid of context for something that's really a very local thing that only one component cares about.Test Plan
Verify splash screen still gets hidden on session init. Verify switching users still works.