<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Fix reply chips not showing some replies (e.g. deleted or empty body
only rendering m.room.message state event)
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [x] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
Tests were AI generated
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Fixes room mentions not being linkified.
Fixes markdown headers not working without 2 new lines.
Fixes random lint stuff.
#### Type of change
- [x] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
## Summary
Closes#701. Stops the timeline from rendering bare day-dividers /
new-message dividers when the underlying event was filtered out at
render time. The orphan-divider pattern in the issue's screenshot was
caused by `useProcessedTimeline` attaching `willRenderDayDivider` to
events that `useTimelineEventRenderer` later returned `null` for (e.g.
membership / profile-change events when `hideMembershipEvents` or
`hideNickAvatarEvents` are on). The render layer would still emit the
divider but skip the event under it.
## Why this matters
7w1's diagnosis on the issue: "this is specifically an issue ... when
there's rooms with lots of hidden events (e.g. joins/leaves, profile
changes) and no other messages, such as announcement channels." The
render now matches that — when an event renders to `null`, its divider
is skipped too.
## Diff
`src/app/features/room/RoomTimeline.tsx`:
```tsx
+const showDividers = renderedEvent !== null;
-const dividers = (
+const dividers = showDividers ? (
<>
{eventData.willRenderDayDivider && ( ... )}
{eventData.willRenderNewDivider && ( ... )}
</>
-);
+) : null;
```
8 lines added, 2 changed.
## Edge case + follow-up
If a day's first hook-eligible event is rendered-null but a later event
renders correctly, the day-divider is lost for that day. That's strictly
better than an orphan divider in the announcement-channel symptom case,
and the proper fix (`useProcessedTimeline` propagates the divider
forward to the first event whose renderer prediction is non-null) is a
larger refactor that can land separately. Happy to follow up with that
if you'd prefer not to take the small fix first.
## Verification
- `pnpm tsc --noEmit` — `No errors found`.
- Manual smoke test path (per issue 7w1 comment): an announcement-style
room dominated by profile-change events stops showing bare day-dividers
between them. A normal chat with mixed messages and joins still renders
dividers correctly because the day's first message-event is the one
carrying the divider, and that event renders fine.
This contribution was developed with AI assistance (Claude Code).
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Fixes #
#### Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
Fixes #
#### Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->
<!-- Please read
https://github.com/SableClient/Sable/blob/dev/CONTRIBUTING.md before
submitting your pull request -->
### Description
<!-- Please include a summary of the change. Please also include
relevant motivation and context. List any dependencies that are required
for this change. -->
(when dark theme)
<img width="232" height="195" alt="image"
src="https://github.com/user-attachments/assets/755ddc4e-046e-4227-a361-eef0ad4717f0"
/>
<img width="247" height="195" alt="image"
src="https://github.com/user-attachments/assets/faf6abdc-fd86-4f0a-9fd2-537fa083bfcd"
/>
(when light theme)
<img width="250" height="191" alt="image"
src="https://github.com/user-attachments/assets/615d13f8-42eb-43f9-be6e-da5acbfe4e16"
/>
<img width="225" height="195" alt="image"
src="https://github.com/user-attachments/assets/48efd21f-03d1-414c-bd6f-cbd477aaac00"
/>
Fixes #
#### Type of change
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update
### Checklist:
- [ ] My code follows the style guidelines of this project
- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] My changes generate no new warnings
### AI disclosure:
- [ ] Partially AI assisted (clarify which code was AI assisted and
briefly explain what it does).
- [ ] Fully AI generated (explain what all the generated code does in
moderate detail).
<!-- Write any explanation required here, but do not generate the
explanation using AI!! You must prove you understand what the code in
this PR does. -->