Improve signals readability and ergonomics#39
Merged
Conversation
Makes more sense, as contexts aren't really reactive, but flow state, as do events and signals
* Operation overload would need to be explicit, so we still need to acess and modify signals through .value
Not really useful right now, will be re-analyzed in future versions
GuilhermeF03
changed the title
GuilhermeF03
changed the title
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
1 participant
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
In order to improve signals readability and expose ergonomics, we attempted to redesign the
SignalsAPIChanges
.updatemethod that accepts a handler where the first arg is the current value(similar to Angular and React).valuefield were keptreactivewas re-namedflow, as contexts didn't really match the package name.Related Issues
Closes #34
Type of Change
Refactor
Checklist
Notes for Reviewers