Skip to content

fix(session-ui): file-reference linkification is core, not a layout preference (#1839) - #1840

Merged
aarontrowbridge merged 1 commit into
mainfrom
fix-file-ref-layout-gate
Oct 22, 2026
Merged

aarontrowbridge merged 1 commit into
mainfrom
fix-file-ref-layout-gate

Conversation

@aarontrowbridge

Copy link
Copy Markdown
Member

Summary

The live-reported bug from the v0.3.8-alpha.1 exercise: every file link in chat silently inert when a panel's stored layout setting had data-new-layout off. Both stages of the file-ref path were layout-gated — the pill tagging (markInlineCode) and the anchor wrapping (markFileLinks) — while the resolver, route, bridge, and 0.3.8 handler all worked but were unreachable. Un-gated both per markExternalLinks' own #270 precedent; the cosmetic code-metadata decoration stays gated. Closes #$ISSUE.

Gates (director-run)

  • New source-assertion tests: RED on the gated source, GREEN on the fix (the repo's component-source-assertion convention — bun's transpiler can't render Solid JSX)
  • Full session-ui component suite: 159/0 (19 files)
  • Drift gate: PASS (988 files, the changed file re-hashed)

The debug trail (layer-by-layer probes: route green via frontdoor+direct, bridge present in the deployed dist bundle, telemetry clean, then the one discriminating DOM observation from Aaron) is in the campaign ledger.

…reference — un-gate markInlineCode + markFileLinks (#1839)

Live report 2026-10-22: with data-new-layout off in a panel's stored
settings, every file path in chat rendered as an inert pill — silently,
zero errors, scripts and markdown alike. The pill tagging (markInlineCode,
decorate) and the anchor wrapping (markFileLinks, the render effect) were
both gated on the new-layout body attribute; the resolver, bridge, and
open-file handler all worked and none of it was reachable.

Un-gated both, per markExternalLinks' own precedent (#270: bridge-handled
links run unconditionally). File links are a capability, not a chrome
preference. Source-assertion tests pin the wiring (the repo's
component-source-assertion convention) — RED on the gated source,
GREEN on the fix; full session-ui component suite 159/0.

Found by Aaron exercising the v0.3.8-alpha.1 build — the release
exercise doing its job.
@coderabbitai

coderabbitai Bot commented Oct 22, 2026

Copy link
Copy Markdown
Contributor

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 3f634be4-d62b-4660-a074-4bc82a398421
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@aarontrowbridge
aarontrowbridge merged commit c4d82a8 into main Oct 22, 2026
5 checks passed
@aarontrowbridge
aarontrowbridge deleted the fix-file-ref-layout-gate branch October 22, 2026 10:49
@aarontrowbridge
aarontrowbridge restored the fix-file-ref-layout-gate branch October 23, 2026 02:42
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