fix: content blocks must be used in Grids - #1331
Conversation
|
Warning: Component files have been updated but no migrations have been added. See https://github.com/yext/visual-editor/blob/main/packages/visual-editor/src/components/migrations/README.md for more information. |
auto-screenshot-update: true
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughMainContentComponent now imports AdvancedCoreInfoCategory. The Content slot’s disallow array adds its entries except “Grid”, while preserving the existing entries. Priority: ⬇️ Low Change: Bug fix Merge Risk: ⚪ Minimal · up to New direct placements of individual content blocks into MainContent are restricted while Grid placement and existing content are preserved. No concrete merge risk is established by the remaining screenshot-only change. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ 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 |
|
huh I thought we had this 🤷 |
Yeah I think it got weird with MainContent allowing them |
Existing content blocks not in Grids won't be affected but any new ones dragged in must be dragged into Grids.
Content Blocks like HoursStatus, Address, and other individual components used in Grid.
Screen.Recording.2026-09-24.at.9.26.27.AM.mov