fix(runtime-tags): compare renderer owners so dynamic tags distinguish instances of the same content - #3378
fix(runtime-tags): compare renderer owners so dynamic tags distinguish instances of the same content#3378DylanPiercey wants to merge 1 commit into
Conversation
🦋 Changeset detectedLatest commit: 7a12d0a The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 28 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 Run ID: ⛔ Files ignored due to path filters (56)
📒 Files selected for processing (76)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
4c1746e to
692774c
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3378 +/- ##
=======================================
Coverage 94.27% 94.28%
=======================================
Files 390 390
Lines 54084 54155 +71
Branches 4386 4392 +6
=======================================
+ Hits 50988 51059 +71
+ Misses 3062 3061 -1
- Partials 34 35 +1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
692774c to
9578ccd
Compare
…h instances of the same content
9578ccd to
7a12d0a
Compare
Description
The dynamic tag change checks compared
renderer?.[RendererProp.Id] || renderer, but the id is the template/section resume id — identical for every instance of the same content section with differentRendererProp.Ownerscopes. Switching a dynamic tag between two instances of the same content (two<define>contents from two instances of one provider tag, or the list-detail pattern<${selected.content}/>) was a silent no-op: no teardown/re-render, and closures stayed subscribed to the old owner's scope. A control case with distinct tag files behaved correctly, pinning the defect to the id comparison.The three change checks (
_dynamic_tag,_dynamic_tag_content, and the DOM_attr_content) now share arendererChangedhelper comparing(id, owner)— content renderer objects are recreated per render, so identity alone would over-fire, while the owner scope is stable per instance. To keep the resume handshake instance-aware (and avoid spurious teardowns that would reset branch state on the first post-resume update), the SSR side now serializes a renderer registered with a scope as its registered reference — which resumes as the owned client renderer — falling back to the bare id exactly as before for instance-less renderers. +24 bytes brotli total.Checklist:
Generated by Claude Code