Make it easier to implement a ComponentWithValue #73
Conversation
This file contains 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.
New components implemented on top of
ComponentWithValueare a bit of a pain to implement, and one of the reasons is that pretty much all implementations add withvalue.get.This PR changes it so that
ComponentWithValueis implemented with arender(value: Ref[T]): Component[Unit](applyRefbasically calls this and returns theRefin the end).It also adds a
Ref#modifyIfhelper method, as one of the pain points was the amount of code that uses something akin toif (condition) value.modify(f).Instead of forcing users to write
if (condition) value.modify(f) else value, they can just use this new helper.