Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUGFIX] Do not eagerly consume modifier args during destruction #1276

Merged

Conversation

pzuraq
Copy link
Member

@pzuraq pzuraq commented Feb 23, 2021

Currently, in the 3.13 modifier capabilities version, we eagerly consume
the arguments that are passed to the modifier when it is destroying.
This can cause issues with backtracking rerender when the state isn't
actually used, and neither is the consumption. This change makes it so
that we don't eagerly consume these arguments during destruction in
general.

@pzuraq pzuraq force-pushed the bugfix/do-not-eagerly-consume-args-during-destruction branch 2 times, most recently from c2cae0b to 77a0d33 Compare February 23, 2021 23:24
package.json Outdated Show resolved Hide resolved
Copy link
Member

@rwjblue rwjblue left a comment

Choose a reason for hiding this comment

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

The other changes seem good, but we should revert the package.json/yarn.lock changes (they are unrelated to the rest of the PR)...

@rwjblue rwjblue added the bug label Feb 24, 2021
@pzuraq pzuraq force-pushed the bugfix/do-not-eagerly-consume-args-during-destruction branch 2 times, most recently from 1bc6756 to 3dc0661 Compare February 25, 2021 19:29
Currently, in the 3.13 modifier capabilities version, we eagerly consume
the arguments that are passed to the modifier when it is destroying.
This can cause issues with backtracking rerender when the state isn't
actually used, and neither is the consumption. This change makes it so
that we don't eagerly consume these arguments during destruction in
general.
@rwjblue rwjblue force-pushed the bugfix/do-not-eagerly-consume-args-during-destruction branch from 995a104 to a6dc74b Compare March 16, 2021 15:29
@rwjblue
Copy link
Member

rwjblue commented Mar 16, 2021

I pinned @handlebars/parser in #1285 (and created #1286 to track down why it needed to happen), and rebased this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants