-
Notifications
You must be signed in to change notification settings - Fork 19
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
fix: Added detectChanges on the flyout open method & possibility to o… #330
Conversation
…pen from datepicker
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tests aren't working atm. Thanks for fixing that!
Yea I noticed that when running it locally. |
Hey @FiestaRuless ik heb het probleem opgelost op de master branch. Je kan deze gewoon binnentrekken en pushen en de CI zou terug moeten werken. |
@TriangleJuice |
Merged in and published under version 6.0.5. |
Moet deze ook gepulished worden op https://nexusrepo.antwerpen.be/service/rest/repository/browse/npm-all/%40acpaas-ui/ngx-flyout/ bijvoorbeeld? |
Nee, de nexusrepo zou deze relatief onmiddellijk moeten oppikken van npmjs. |
PR Checklist
This PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
When using ngx-forms it's datepicker, a flyout is used to open the calendar. This can be done by clicking on the icon but the method open() also exists so you can open using code. When this method is called, the state gets changed and the value 'this.isOpened' is changed to true. But the HostBinding does not update and set the class 'is-open'. The updated value didn't persist to the view. DetectChanges was added to update the view.
Issue Number: N/A
What is the new behavior?
When directly calling the open() method, the class 'is-open' is added.
Does this PR introduce a breaking change?
Other information
Resolved issues