-
Notifications
You must be signed in to change notification settings - Fork 382
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
How to filter a PeoplePicker #1657
Comments
Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible. |
Thank you for submitting your first issue to this project. |
Hi @cardinalpipkin, I've created a PR that should match your case.
Hope this answer your issue! |
@GuidoZam - apologies, but I'm a novice at this area of PR's(!). How will I know if and when this PR you kindly created is approved and deployed? And will it be in a future version or applied to the existing version? |
Hi @cardinalpipkin no worries we've all been novices 😄 To follow the status of the PR you can check it here. |
@cardinalpipkin really sorry for the delay on this, the PR is now merged and the feature will be available in the beta release within a few minutes and also part of the next main release (not sure when this will happen at this point). |
Category
[ ] Enhancement
[ ] Bug
[/] Question
├── @fluentui/react-components@9.31.0
├── @microsoft/teamsfx-cli@1.2.6
├── @pnp/logging@3.18.0
├── @pnp/sp@3.18.0
├── @pnp/spfx-controls-react@3.15.0
└── react-icons@4.11.0
Version
Please specify what version of the library you are using: [ 3.15.0 ]
Question
I am trying to filter an sp pnp people picker:
PeoplePicker - @pnp/spfx-controls-react
I want to filter based on whether the users found have a certain @domain.com
Is there an out of the box solution that comes with the control or is it something I will have build around it?
It's been suggested I use
import { PeoplePickerFilter } from '@pnp/spfx-controls-react';
but I get an error saying it doesn't exist on @pnp/spfx-controls-react:
How to filter it?
The text was updated successfully, but these errors were encountered: