Added refsFn to computed #257
Open
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
…ng tracked even if one of them is falsy.
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.
Added refsFn to computed, to ensure all references are reactively being tracked even if one of them is falsy.
Reactivity in computed functions is setup when an internal ref is being accessed. In some cases the dependency between references can cause refs to never be accessed and as a result changes to those refs will never trigger the reactivity and reevaluation of the computed prop.
Reported on discord: https://discord.com/channels/1020300788016353311/1329146069518651496
Playground example: https://playground.lightningjs.io/#QLnOkvYbQQiQ