Make useSession().start more stable
#1233
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.
Per a note in #1230 (comment), I've made a follow up change which does some work to make
session.starthave a fully stable reference.With these changes, a snippet like the below will now work as expected:
As background context - the reason that
session.start's reference changed so often was because it had a dependency onwaitUntilConnected/agent.waitUntilAvailable, and each of these themselves had dependencies onsession.connectionStateandagent.state, which changed often. There wasn't really much of a con to making a localized copy of this state as a ref so after I did that in both cases the references became stable and those stable references cascaded up to makesession.startstable!