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 release] Ensure user lifecycle hooks are untracked #19193

Merged
merged 1 commit into from
Oct 13, 2020

Conversation

pzuraq
Copy link
Contributor

@pzuraq pzuraq commented Oct 13, 2020

When we refactored the VM to use autotracking internally, some lifecycle hooks were tracked that previously weren't on classic components. This PR ensures those hooks are no longer tracked, maintaining their previous behavior.

Fixes #19192

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.

Should these be untracked though? Seems like they should at least emit a deprecation, no?

When we refactored the VM to use autotracking internally, some lifecycle
hooks were tracked that previously weren't on classic components. This
PR ensures those hooks are no longer tracked, maintaining their previous
behavior.
@pzuraq pzuraq force-pushed the bugfix/ensure-user-lifecycle-hooks-are-untracked branch from 0a1cbee to 35ca781 Compare October 13, 2020 19:17
@pzuraq pzuraq merged commit ae672e5 into master Oct 13, 2020
@pzuraq pzuraq deleted the bugfix/ensure-user-lifecycle-hooks-are-untracked branch October 13, 2020 22:15
@rwjblue
Copy link
Member

rwjblue commented Oct 14, 2020

FWIW, we chatted RE: my concern above and decided that we did not want to introduce deprecations at the moment for this. Specifically: resolving these deprecations would largely just be a waste of work (since the real path forward is migration to @glimmer/component which doesn't have these issues to begin with).

this.foo = 123;
}
},
template: '{{this.baz}}',
Copy link
Contributor

Choose a reason for hiding this comment

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

Dumb question when reading the diff, should it be {{this.foo}}?

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

Successfully merging this pull request may close these issues.

Backtracking assertion "more aggressive" in 3.22
3 participants