[draft] enable "all custom fields"/"all fields" wildcards in SearchKit #34192
+184
−18
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
Enable adding "all custom fields"/"all fields" for an entity when building a SearchKit.
This is draft and needs some cleanup but wanted to give you a sense of what I'm trying to do @colemanw
Before
After
Technical Details
A chunk of this is just de-lodashing some functions.
Then it's breaking the assumption that
savedSearch.api_params.selectcorresponds one-to-one to the columns in search admin.