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 lts + beta] Ensure modifiers do not run in FastBoot modes. #18071

Merged
merged 4 commits into from
Jun 4, 2019

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Jun 3, 2019

Fixes #17949

Note: the fix is split into two different commits to make backporting easier

CvX and others added 4 commits June 3, 2019 17:47
Prior to this change, custom modifier managers were invoked during
non-interactive rendering invocations as well as interactive. In
practice, that resulted in custom modifiers erroring whenever they ran
in FastBoot / SSR environments.

This change, ensures that the interactive / non-interactive state is
threaded through to the required infrastructure to avoid invoking _any_
hooks on custom modifier managers when running in non-interactive modes.
Since `{{on}}` is a "special" built-in modifier manager, the generic
fixes for custom modifier managers do not fix `on`. This applies the
same general fix, and ensures that `{{on}}` is a no-op in FastBoot mode.
@CvX
Copy link
Contributor

CvX commented Jun 3, 2019

I've tried it out in my production app and it does indeed work as intended! 🚀

@rwjblue rwjblue merged commit a573ab5 into emberjs:master Jun 4, 2019
@rwjblue rwjblue deleted the modifier-destroy branch June 4, 2019 13:46
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.

destroyModifier is called in SSR mode
2 participants