feat: add label field to SelectedFacet for CMS identification#1609
feat: add label field to SelectedFacet for CMS identification#1609dan-liberato wants to merge 2 commits into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe ChangesSelectedFacet label extension
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Tagging OptionsShould a new tag be published when this PR is merged?
|
What is this contribution about?
This PR adds an optional
labelfield to theSelectedFacetinterface to improve the configuration experience in the Deco CMS Admin.Currently,
SelectedFacetentries only exposekeyandvalue, which can make it difficult for editors to identify what each facet represents in a list.The new
labelfield provides a human-readable description, such ascategory-1 > CollectionorproductClusterIds > 123, that appears in the Admin UI without affecting the search query behavior.Impact
Summary by cubic
Add an optional
labelto SelectedFacet to show a human-readable name in Deco CMS Admin (e.g., "category-1 > Collection" or "productClusterIds > 123"). No search or runtime changes; fully backward compatible.Written for commit 96db425. Summary will update on new commits.
Summary by CodeRabbit