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

feat: allow open menu if max items limit is reached #2054

Merged
merged 5 commits into from
Jun 3, 2022

Conversation

windischb
Copy link
Contributor

Hi!
As we have the need to open the menu, even if the maxSelectedItems limit is reached, i have added an option for that.
There is also an open Issue(#1447) which this PR fixes.

@windischb windischb changed the title Allow open menu if max items limit is reached feat: allow open menu if max items limit is reached Mar 8, 2022
@varnastadeus
Copy link
Member

@windischb thanks for your contribution. Looking back at the feature I would say this should be the default behavior as it improves UX. Can you change the code without introducing new property? Also, we should consider whether to release this under breaking change 🤔

@windischb
Copy link
Contributor Author

@varnastadeus of course!
I have removed the property and all added parts like examples.
Now it's just one small code change left, but it does what it should.
Hopefully this is what you have in mind...

varnastadeus
varnastadeus previously approved these changes May 27, 2022
@varnastadeus varnastadeus dismissed their stale review May 27, 2022 10:04

build check is missing

@varnastadeus varnastadeus merged commit 0400ab3 into ng-select:master Jun 3, 2022
@github-actions
Copy link

github-actions bot commented Jun 3, 2022

🎉 This PR is included in version 8.3.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants