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

fix: Added detectChanges on the flyout open method & possibility to o… #330

Merged
merged 2 commits into from
Jan 16, 2024

Conversation

FiestaRuless
Copy link
Contributor

PR Checklist

This PR fulfills the following requirements:

  • The commit message follows our guidelines: Contributing guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)
  • A changelog entry was added

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.io application / infrastructure changes
  • Other... Please describe:

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?

  • Yes
  • No

Other information

Resolved issues

Copy link
Contributor

@TriangleJuice TriangleJuice left a 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!

@FiestaRuless
Copy link
Contributor Author

Yea I noticed that when running it locally.
But the error is of something withing node_modules/@types/node.
Doesn't really have something to do with my changes so I'm not really sure how to solve this?
Should I update that specific package?

@TriangleJuice
Copy link
Contributor

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.

@FiestaRuless
Copy link
Contributor Author

@TriangleJuice
Normaal zou hem gemerged moeten zijn

@NicolasYapla NicolasYapla merged commit 62853bc into digipolisantwerp:master Jan 16, 2024
1 check passed
@NicolasYapla
Copy link
Contributor

Merged in and published under version 6.0.5.

@FiestaRuless
Copy link
Contributor Author

Moet deze ook gepulished worden op https://nexusrepo.antwerpen.be/service/rest/repository/browse/npm-all/%40acpaas-ui/ngx-flyout/ bijvoorbeeld?

@TriangleJuice
Copy link
Contributor

Nee, de nexusrepo zou deze relatief onmiddellijk moeten oppikken van npmjs.

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