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] Ensure view registry is provided to components. #11270

Merged
merged 1 commit into from
May 25, 2015

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented May 25, 2015

No description provided.

rwjblue added a commit that referenced this pull request May 25, 2015
…-down

[BUGFIX beta] Ensure view registry is provided to components.
@rwjblue rwjblue merged commit 1d91c95 into emberjs:master May 25, 2015
@rwjblue rwjblue deleted the ensure-view-registry-is-passed-down branch May 25, 2015 16:35

runAppend(view);

equal(innerTemplate._viewRegistry, viewRegistry);
Copy link
Member

Choose a reason for hiding this comment

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

should this also test that w/e uses viewRegistry works correctly?

Copy link
Member Author

Choose a reason for hiding this comment

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

By default _viewRegistry is Ember.View.views, but that does not work in the fastboot or multiple app scenario (because there are two different view registries).


This change, ensures that the _viewRegistry is passed down through the various views/components created during render (it was previously not passed through). It does not actually test that things use _viewRegistry (though they should).

Copy link
Member Author

Choose a reason for hiding this comment

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

@stefanpenner - Thanks for poking me into looking into the usage side of this, #11290 fixes an issue with the event dispatcher that broke multiple apps on the page...

Copy link
Member

Choose a reason for hiding this comment

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

👍

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.

2 participants