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

Fixed misprint with menu components array #1449

Merged
merged 1 commit into from
Apr 5, 2018
Merged

Fixed misprint with menu components array #1449

merged 1 commit into from
Apr 5, 2018

Conversation

AVykhrystyuk
Copy link

@AVykhrystyuk AVykhrystyuk commented Apr 4, 2018

Currently destroyed menu components are not removed from MdlMenuRegisty due to misprint in Array.prototype.splice.
This leads to continuous calls of MdlMenuComponent.hide() inMdlMenuRegisty.hideAllExcept() for menu components that are already destroyed.
In my use case this leads to TypeError: Cannot read property 'toArray' of undefined when user clicks on any alive menu drop-down component.
This PR should fix the misprint so the components are removed correctly from MdlMenuRegisty.

Commit summary:

  • fixed the build error: Can not find 'protractor' typings
  • fixed misprint with menu components array

- fixed missprint with menuComponents array
@AVykhrystyuk
Copy link
Author

@mseemann Could you please take a look at this PR?

@coveralls
Copy link

Coverage Status

Coverage increased (+0.0003%) to 99.476% when pulling f300b03 on AVykhrystyuk:bugfix/menu-components-missprint into e93f79a on mseemann:master.

@mseemann
Copy link
Owner

mseemann commented Apr 5, 2018

@AVykhrystyuk thx! will be in the next release.

@mseemann mseemann merged commit 570e05f into mseemann:master Apr 5, 2018
@AVykhrystyuk AVykhrystyuk deleted the bugfix/menu-components-missprint branch April 6, 2018 07:20
@AVykhrystyuk
Copy link
Author

@mseemann Thanks. May I know some approximate date for the next release?

@mseemann
Copy link
Owner

mseemann commented Apr 6, 2018

the next release will be 5.0.0. There are some breaking changes that needs some more time. If you need this urgent, please create a PR against the angular4 branch. after that i can publish a 4.0.9 version. thx

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.

4 participants