Matt Van Horn e53c26f934 fix(timeline): suppress dividers when the underlying event renders null
Closes #701

The hook hands the renderer a `willRenderDayDivider` / `willRenderNewDivider`
flag attached to the FIRST event of a new day (or the readUptoEventId
boundary). The render layer in RoomTimeline always emitted those dividers
even when `useTimelineEventRenderer` returned `null` for the event itself
— for example when `hideMembershipEvents` / `hideNickAvatarEvents` /
`hideMemberInReadOnly` filtered the underlying event out at render time.

Result: announcement channels and similar rooms whose only events on a
given day are hidden (joins/leaves/profile changes) showed a bare day
divider with no message under it. Same orphan pattern produced the
"dates showing without content" complaint in #701.

Fix: gate the dividers JSX on `renderedEvent !== null`. When the event
renders null, the dividers are skipped too. When at least one event of
a day passes the renderer, the divider is attached to it the same way
as before.

Edge case: a day where the first hook-eligible event is rendered as null
but a later event renders correctly will lose the day divider entirely.
That is strictly better than an orphan divider in the symptom case the
issue reports, and the proper fix (propagate the divider forward in
useProcessedTimeline based on render prediction) is a larger refactor
that can land separately.
2026-04-26 03:33:51 -07:00
2026-04-19 16:47:05 +02:00
2026-03-05 22:34:11 -06:00
2026-04-12 10:50:50 +03:00
2026-03-04 19:21:00 -06:00
2026-04-10 03:16:07 +00:00
2026-03-13 21:38:40 -05:00
2026-03-12 00:31:27 +01:00
2026-04-19 16:47:05 +02:00
2026-04-16 22:15:13 -05:00
2023-02-24 17:28:04 +05:30
2026-04-16 22:15:13 -05:00
2026-04-16 22:15:13 -05:00
2026-04-16 22:15:13 -05:00
2026-04-16 22:15:13 -05:00

Sable

A Matrix client built to enhance the user experience with quality-of-life features, cosmetics, utilities, and sheer usability. See the changelog.

Soon to be replaced desktop apps can be downloaded here. They auto-update by pulling the website.

Join our matrix space here to discuss features, issues, or meowing.

Forked from Cinny.

Getting started

The web app is available at app.sable.moe and gets updated on frequently, as soon as a feature is deemed stable.

You can also download our desktop app for windows and linux from releases.

Self-hosting

You have a few options for self hosting, you can:

  1. Run the prebuilt docker container.
  2. Deploy on a site like GitLab Pages. Jae has a guide here.
  3. Build it yourself.

Docker

Prebuilt images are published to ghcr.io/sableclient/sable.

  • latest tracks the current dev branch image.
  • X.Y.Z tags are versioned releases.
  • X.Y tags float within a release line.
  • Pushes to dev also publish a short commit SHA tag.

Run the latest image with:

docker run --rm -p 8080:8080 ghcr.io/sableclient/sable:latest

Then open http://localhost:8080.

If you want to override the bundled config.json, mount your own file at /app/config.json:

services:
  sable:
    image: ghcr.io/sableclient/sable:latest
    ports:
      - '8080:8080'
    volumes:
      - ./config.json:/app/config.json:ro

Build it yourself

To build and serve Sable yourself with nginx, clone this repo and build it:

pnpm i # Installs all dependencies
pnpm run build # Compiles the app into the dist/ directory

After that, you can copy the dist/ directory to your server and serve it.

  • In the config.json, you can modify the default homeservers, feature rooms/spaces, toggle the account switcher, and toggle experimental simplified slilding sync support.

  • To deploy on subdirectory, you need to rebuild the app youself after updating the base path in build.config.ts.

    • For example, if you want to deploy on https://sable.moe/app, then set base: '/app'.

Local development

Tip

We recommend using a version manager as versions change quickly. fnm is a great cross-platform option (Windows, macOS, and Linux). NVM on Windows and nvm on Linux/macOS are also good choices. Use the version defined in .node-version.

Execute the following commands to start a development server:

fnm use --corepack-enabled # Activates the Node version and enables corepack
# If you not using fnm, install corepack manually: npm install --global corepack@latest
corepack install # Installs the pnpm version specified in package.json
pnpm i # Installs all dependencies
pnpm run dev # Serve a development version

To build the app:

pnpm run build # Compiles the app into the dist/ directory

Deployment and infrastructure

Deployment workflows and infrastructure details live in infra/README.md.

S
Description
No description provided
Readme AGPL-3.0
107 MiB
0 Stars 1 Watchers 0 Forks
Languages
TypeScript 93.2%
Rust 5.2%
JavaScript 0.8%
Kotlin 0.2%
CSS 0.2%
Other 0.3%