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 beta] Bump Glimmer #14520

Merged
merged 2 commits into from
Oct 26, 2016
Merged

[BUGFIX beta] Bump Glimmer #14520

merged 2 commits into from
Oct 26, 2016

Conversation

chancancode
Copy link
Member

This pulls in two glimmer-engine bugfixes:

  • local variables (block params) should always win over helpers
  • stateful/class-based helpers used in {{#if (my-helper ...)}} and other block arguments position are destroyed when the block syntax switches from default to inverse (and vice versa)

Fixes #14351, #14413

This commit fixes a bug where `OutletComponentReference`
inadvertently relied on broken behavior: it returned `null`, assuming
that that would cause the reference to be rebuilt. But
glimmerjs/glimmer-vm#337 fixed the underlying bug, causing the reference to
be properly cached. As a result, we need to remember that we rendered a
`null` component, so that swapping back to the original component
replaces the empty component with the rendered component.
This pulls in two glimmer-engine bugfixes:

- local variables (block params) should always win over helpers
- stateful/class-based helpers used in `{{#if (my-helper ...)}}` and
  other block arguments position are destroyed when the block syntax
  switches from default to inverse (and vice versa)

Fixes emberjs#14351, emberjs#14413
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.

Getting "Uncaught Error: infinite rendering invalidation detected" with 2.9-beta3
1 participant