Only filter post retrieval of entities for start nodes if working with entities that support start nodes #18287
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…h entities that support start nodes.
nikolajlauridsen
approved these changes
Feb 17, 2025
nikolajlauridsen
deleted the
v13/bugfix/all-members-search-from-picker
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prerequisites
Fixes: #18286
Description
As the issue notes, you can't retrieve any members via the "All members" view of the member picker (although you do get the paging information). This was due to some code looking to filter post retrieval into a paged model for user start nodes.
I've modified this so it only applies for documents and media, which are the only entities that support start nodes.
To Test: