-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
destroyModifier is called in SSR mode #17949
Comments
Thank you for reporting (and the reproduction)! |
This issue is also present when using the on modifier from the feature flag under canary.
|
I've just run up against this issue. Whereas ember.js/packages/@ember/-internals/glimmer/lib/environment.ts Lines 72 to 82 in 85de05f
ember.js/packages/@ember/-internals/glimmer/lib/modifiers/custom.ts Lines 43 to 46 in 85de05f
Not sure of the best solution of getting the |
@willviles thanks for the insight! Here's my stab at the problem: master...CvX:modifiers-destroy-non-interactive The "bugfix" 😂 is atrocious and brittle, but it's a start: a. it has tests, so at the very least that could lead to an actual fix |
@CvX - Mind sending that in as a PR? |
OK, #18071 should fix. |
Thank you @CvX for pushing up those tests! |
@rwjblue ah, sorry for the slow response on my side! Thank you for the actual fix. 🙂 I'm checking out the code right now, and will try it out in my app in a moment. 🙂 |
Using modifiers with FastBoot (SSR) should result in them not been executed at all in FastBoot, leaving it to be only executed in client environment.
Currently:
installModifier
is not called in SSR, however,destroyModifier
is.Expected:
destroyModifier
to not be called in SSR.Reproduction is here: https://github.com/josemarluedke/--ember-modiers-fastboot
The text was updated successfully, but these errors were encountered: