Refactor element state model to support reactive framework integration#85
Merged
Refactor element state model to support reactive framework integration#85
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
ForesightElementDatawith an immutableForesightElementStatesnapshot that is swapped on every change, enabling compatibility with React'suseSyncExternalStoreand Vue'sshallowRefsubscribe/getSnapshotonForesightRegisterResultso framework adapters can reactively bind to element state without polling or manual event wiringForesightElementInternal) from the public state surface, using aDerivedMapViewto prevent leaking internals throughregisteredElementscallbackInfoobject into top-level state fields (isPredicted,isCallbackRunning,hitCount,durationMs,status,error, etc.)useForesight) to consume the new state shapesubscribe/getSnapshotlifecycle,DerivedMapView, re-registration, and related edge casesThis is the first step towards creating pre-made framework adaptors