feat: Add isReady state property
#3778
Merged
+55
−8
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.
Adds a lazily populated
isReadystate property that is populated as a side-effect ofensureCanUsePlatform(renamed fromassertCanUsePlatform).Note
Introduces
isReadytoSnapControllerstate, lazily populated via new#ensureCanUsePlatform, and updates flows/tests accordingly.state.isReady(defaultfalse); include inincludeInStateLogsandincludeInDebugSnapshot; not persisted/used in UI.#assertCanUsePlatformwith#ensureCanUsePlatformthat waits onboarding, setsisReadybased ondisableSnaps, and asserts availability.#ensureCanUsePlatformininit(),updateRegistry(),startSnap(),installSnaps(),#updateSnap(), andhandleRequest().isReadytofalseinclearState().SnapController:initsetsisReady.isReadyin debug/state logs and post-clearStatestate, and minor timing adjustments.Written by Cursor Bugbot for commit 2df985d. This will update automatically on new commits. Configure here.