Skip to content

Use new generic signals across web core#1009

Draft
ava-cassiopeia wants to merge 3 commits intoavac-generic-signalsfrom
avac-web-core-generic-signals
Draft

Use new generic signals across web core#1009
ava-cassiopeia wants to merge 3 commits intoavac-generic-signalsfrom
avac-web-core-generic-signals

Conversation

@ava-cassiopeia
Copy link
Copy Markdown
Collaborator

Now that I've got these generic signals in a good place (see #1008), this PR actually uses them across web core.

Note: this is a breaking change for any downstream implementations, I don't expect them to compile once they pull this in. But, we have version pinning as-of #996, so we can make that upgrade incrementally. It does mean we'll probably want to publish web core before upgrading those libraries.

@ava-cassiopeia ava-cassiopeia self-assigned this Mar 27, 2026
@github-project-automation github-project-automation bot moved this to Todo in A2UI Mar 27, 2026
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a pluggable signal abstraction via the FrameworkSignal interface, refactoring the state and rendering layers to support multiple reactive frameworks through a generic signal kind parameter. Feedback indicates that the removal of explicit batching in DataModel could lead to performance issues and recommends adding a batch method to the new abstraction. Furthermore, a misleading comment in DataContext concerning the reactivity of function arguments should be addressed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

1 participant