SearchKit - allow searches based on relationships #20558
Merged
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.
Overview
Allows searches to be based on relationships:
Before
Searches with Contact as an entity could add Related Contacts as a join, but the base table could not be relationship.
After
Searches can use Relationships as the base entity, and default action links are provided (view/edit/delete relationship)
Technical Details
This makes it possible to use a bridge entity for the base of a search (only if it is annotated
@searchable primary|secondary
)It also ensures that fields needed for links are available in search displays (previously it ensured ID was returned but some links require other fields as well).
Comments
This gets us inches away from being able to replace the Relationships tab on the contact summary screen. If SearchKit and Afform were force-enabled on every install, I'd do it right now.