Add component: key support to block config resolution - #73
Add component: key support to block config resolution#73helmutkaufmann wants to merge 3 commits into
Conversation
Blocks may declare a top-level component: <key> to derive default fields from a CMS component's defineProperties(), with the block's own fields always taking precedence on collision.
|
Warning Review limit reached
Next review available in: 59 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
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 |
Split out of #68 (closed in favor of smaller, focused PRs).
Summary
component:key to derive default fields from a CMS component'sdefineProperties(), instead of (or alongside) hand-writtenfields:.fields:always take precedence over fields derived from the component on key collision. If the component can't be resolved, a warning is logged and the block's own fields are used as-is.See the README section "Deriving fields from a component" for usage.
Test plan
tests/classes/BlockManagerTest.phpcovering property merge, override precedence, and unresolvable-component handling, plus an end-to-end test via a real.blockfilephp artisan winter:test -p Winter.Blocks)