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

Ensure view registry entries can be unregistered properly. #14100

Merged
merged 1 commit into from
Aug 19, 2016

Conversation

rwjblue
Copy link
Member

@rwjblue rwjblue commented Aug 19, 2016

When the register / unregister functions were moved from the ViewSupportMixin to the renderer, I didn't properly update them to use the provided view's elementId and was instead using this.elementId (on the renderer) which was obviously undefined.

This meant that we were holding on to a reference of all views/components ever created (since they were never being released from the viewRegistry). 😭

When the `register` / `unregister` functions were moved from the
`ViewSupportMixin` to the renderer, I didn't properly update them to use
the provided `view`'s `elementId` and was instead using `this.elementId`
(on the renderer) which was obviously undefined.

This meant that we were holding on to a reference of all
views/components ever created (since they were never being released from
the `viewRegistry`). 😭
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.

1 participant