Skip to content

Regression bridge entangled to itself - #63

Merged
koculu merged 3 commits into
mainfrom
regression-bridge-entangled-to-itself
Feb 22, 2026
Merged

koculu merged 3 commits into
mainfrom
regression-bridge-entangled-to-itself

Conversation

@koculu

@koculu koculu commented Feb 22, 2026

Copy link
Copy Markdown
Member

Fixes component-prop retargeting regressions introduced in single-prop bridge syncing.

What changed

  • Prevented bridge self-sync teardown in single-prop:
    • early return when forwarded bridge source equals current prop target (ctxKey === value).
  • This preserves the real source↔bridge entangle after prop shadowing in component context.

Why

  • After selectedHost replacement, first r-for mutation in component-prop path could target stale tenants (or throw in app builds) because source↔bridge link was unintentionally cleared.

Tests

  • Added regression coverage in tests/directives/r-for.spec.ts for:
    • switching selectedHost via component prop
    • first tenant add after switch should use new host list
  • Revalidated existing r-model retargeting coverage in tests/directives/model.spec.ts.

@koculu
koculu merged commit 21fd105 into main Feb 22, 2026
1 check passed
@koculu
koculu deleted the regression-bridge-entangled-to-itself branch February 22, 2026 04:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant