* feat: Filter DSL for collections.list
Adds the structured `filters` expression language to collections.list,
matching documents.list and documents.search. Supported fields are name,
createdAt, updatedAt, archivedAt, createdById and permission, each validated
against its column type at the input layer.
Deprecates the ad-hoc `query` and `statusFilter` params, which now translate
into filter leaves so that one code path serves both shapes, and returns a 400
when a caller combines them with `filters`.
Note that `query` matching is no longer accent-insensitive, as the unaccent
comparison is replaced by the shared iLike conversion.
* fix: Make filter expressions assignable to a JSON request body
Filters are sent as a JSON body, but `FilterCondition` and `FilterGroup` were
interfaces, which TypeScript does not give an implicit index signature, and
`FilterValue` admitted a `Date` that JSON cannot carry. Both stores worked
around this by asserting the request body to JSONObject, which suppressed
checking of every other field as well.
Declare the two shapes as type aliases and drop `Date` from the value union so
a filter type-checks against the request body directly, and remove the
assertions from the collection and document stores.
* feat: Restrict filter fields to a set of accepted values
Add an optional `values` set to a filter field definition, checked against
scalar and array values at the input layer so that an unsupported value returns
a 400 rather than an empty result or, for a field backed by a Postgres enum, a
database error. A field with a fixed value set is matched exactly, so pattern
operators are rejected for it in the same way as for non-text columns.
Apply it to `permission` on collections.list.
* refactor: Build the list_collections name filter with the filter DSL
The MCP tool carried its own copy of the unaccent name comparison that
collections.list used before it moved to the DSL. Build the clause with
buildWhere instead, so both paths match names the same way, and drop the
replacements plumbing it needed.
* fix: Selection toolbar not displaying on mobile
The mobile branch of FloatingToolbar rendered nothing until `position.visible`
was true, but `usePosition` only reports a visible position once the menu
element has been measured through `menuRef`. On desktop the wrapper is always
mounted (it animates in via opacity) so the ref is populated on first render,
while on mobile the toolbar is the only thing that mounts the ref — leaving it
permanently null and the bar never displayed.
Gate the mobile bar on there being toolbar content instead. Position is
irrelevant on mobile: the bar is fixed to the bottom of the viewport and its
vertical offset is owned by useKeyboardStickyOffset.
Also size the bar with border-box and center its content vertically, so the
declared 60px is the height of the bar rather than 60px of content plus
padding with the buttons pinned to the top.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GhGyxA663bMFZ1NxBhLAoF
* fix: Keep the mobile selection toolbar visible while editing
On mobile the toolbar is a bar docked above the on-screen keyboard rather than
a floating menu anchored to the selection, but it was only rendered while
something was selected — so it appeared and vanished as the selection came and
went while typing.
The formatting menu was already written for this: `canFormatBlock` shows
headings, quotes, toggles and list indent/outdent precisely when the selection
is empty on mobile, mirroring `canFormatInline` for selected text. That branch
was unreachable, as an empty selection always resolved the toolbar to nothing.
Show the menu whenever the editor is focused on mobile, so the bar carries
block formatting for a bare cursor and swaps to inline formatting on selection.
Visibility is derived at render rather than folded into `activeToolbar` so that
focus moving into the link editor's input cannot tear down a toolbar the user
opened. Focus is threaded to widgets through WidgetProps.
Tapping the bar now also prevents the default action of mousedown, keeping
focus (and the keyboard) in the editor. Without it a tap would blur the editor
and unmount the bar before the tap became a click; fields inside the bar are
excluded so the link editor still takes focus.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GhGyxA663bMFZ1NxBhLAoF
* fix: Mobile toolbar is not visible
* Update mobile toolbar styling
fix: Does not account for stored marks
---------
Co-authored-by: Claude <noreply@anthropic.com>
* fix: Search result context cut mid-word by earlier highlights
The snippet indexes were calculated against the plain document text, then used
to slice the highlighted copy. Every highlight before the slice start adds seven
characters, so the snippet began too late and could open inside a bold tag.
Slice first and highlight the slice, so both indexes apply to the same string.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Feedback
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Only show editing stats toggle when viewing a document
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Default isViewing to false
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
The contents lists headings up to level four, but tracked the active heading
across every heading in the document. Scrolling into a level five or six
section selected a heading with no entry in the list, so the highlight
disappeared until the next listed heading came into view.
The level filter now runs once, up front, and the active heading tracking,
indentation base, empty check and render all read the same list. Prefix labels
are still computed over every heading so the numbering keeps matching the
document.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: New German translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Polish translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Vietnamese translations
* fix: New Dutch translations
* fix: New Dutch translations
* fix: New Thai translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New English, United Kingdom translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Spanish translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New Norwegian Bokmal translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New English, United Kingdom translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New English, United Kingdom translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New English, United Kingdom translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Polish translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New English, United Kingdom translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Spanish translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Thai translations
* fix: New Swedish translations
* fix: New Portuguese translations
* fix: New Ukrainian translations
* fix: New Vietnamese translations
* fix: New Persian translations
* fix: New Spanish translations
* fix: New Catalan translations
* fix: New Czech translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Dutch translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Chinese Simplified translations
* fix: New Chinese Traditional translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Indonesian translations
* fix: New Persian translations
* fix: New Thai translations
* fix: New English, United Kingdom translations
* fix: New Norwegian Bokmal translations
* fix: New French translations
* fix: New Spanish translations
* fix: New Danish translations
* fix: New German translations
* fix: New Hebrew translations
* fix: New Hungarian translations
* fix: New Italian translations
* fix: New Japanese translations
* fix: New Korean translations
* fix: New Polish translations
* fix: New Portuguese translations
* fix: New Swedish translations
* fix: New Turkish translations
* fix: New Ukrainian translations
* fix: New Vietnamese translations
* fix: New Portuguese, Brazilian translations
* fix: New Thai translations
Shared links return markdown when the client asks for it, but there was no
way to discover this short of guessing the .md suffix.
- Vary on Accept so shared caches key the two representations correctly
- Send a Link rel="alternate" header, discoverable with a HEAD request
- Emit a matching link tag alongside the canonical in the head
- Apply the same cache directives to markdown as the HTML response
* feat: Record who deleted a document
The trash inferred the deleting user from lastModifiedById, so a nested page
kept whoever last edited it and deleting a document rewrote its edit history.
Add a dedicated deletedById column and set it from the base model.
- Migration adds the column, backfills from lastModifiedById, and validates the
foreign key without holding an exclusive lock. The backfill runs in batches
against a temporary index covering only the rows still to write, so it stays
linear on a large table, and every statement is idempotent because the
migration cannot run in a transaction.
- ParanoidModel records the acting user on destroy and clears it on restore,
for any model that has the column. Sequelize soft deletes with the same UPDATE
that stamps deletedAt, so the value costs no extra query.
- Deleting a document no longer touches lastModifiedById on its descendants.
- Present the deleting user, batched in presentDocuments, and use it for the
trash notice and the document meta line rather than the last editor.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Do not overwrite an eager loaded deleting user when batching
The batch lookup in presentDocuments skipped documents that already carried the
association, but the assignment loop ran for all of them, so a document that
arrived with deletedBy loaded was reset to null and fell back to a per-document
query. Assign only where the association is missing, and deduplicate the ids so
a page deleted by one person asks for one row rather than one per document.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Recover from closed IndexedDB connections in store persistence
StorePersistence cached a single IDBDatabase forever, so once the browser
or another tab closed the connection every subsequent hydrate, flush and
clear threw against a dead handle.
- Close and forget the connection on versionchange, so another tab is
never blocked from deleting or upgrading the database
- Discard the cached connection on close, open error and blocked, and
retry once against a fresh connection when one was closed underneath us
- Close open connections before deleteAllDatabases removes them, which
also stops logout recreating the databases it just deleted
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Cancel pending writes when store persistence is disabled
A debounced flush scheduled before disabling would still fire, reopening
and recreating the database that deleteAllDatabases had just removed.
* fix: Crash opening document menu on mobile
The heading numbering submenu added to the document display options is
rendered through the `append` slot of `DropdownMenu`. On desktop that slot
lands inside the menu content, but on mobile it is rendered into a drawer,
which has no menu root for the Radix submenu primitives to attach to — so
opening the document overflow menu on mobile threw "`MenuSub` must be used
within `Menu`" and took down the page.
Flatten the submenu into an inline group of options on mobile, matching the
toggles it sits alongside.
Fixes OUTLINE-CLOUD-D1X
Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V5ExrfehTYgotb8d2aoMvK
* fix: Match heading prefix color to the heading anchor
The heading numbering prefix was drawn with the secondary text color while
the `#` anchor beside it uses the primary text color at 75% opacity. The
two read as the same tone in light mode, but diverge visibly in dark mode
where the primary text color is much brighter.
Draw the prefix from the same color and opacity as the anchor so the two
match in both themes.
Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V5ExrfehTYgotb8d2aoMvK
* fix: Heading prefix missing when printing
The print stylesheet hides the heading pseudo element to keep the H1–H6
level labels out of print. That pseudo element also carries the heading
numbering prefix, so printing or exporting a numbered document dropped its
numbers.
Qualify the print selectors the same way the level labels themselves are,
so only the labels are hidden and the prefix still prints.
Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01V5ExrfehTYgotb8d2aoMvK
* Update Styles.ts
The client serializes all @Field properties on save, so documents created
before the preferences column existed post `preferences: null`, which the
update and create schemas rejected.
raw-body throws a 500 'stream is not readable' when the request stream is
already destroyed at parse time, which means the client went away. Map it to
ClientClosedRequestError so it reports 499 and is not sent to the bug tracker.
* feat: Filter DSL for users.list
Add the structured filter expression language already used by documents.list
and documents.search to users.list, over an allowlist of id, name, email,
role, createdAt, updatedAt, lastActiveAt and suspendedAt.
Supersedes the ad-hoc ids, emails, role and filter parameters, which are now
deprecated and translated into the DSL so a single path builds the query. The
same translation backs the list_users MCP tool, which held a duplicate copy of
the status handling.
Field specs gain an optional value allowlist, so an unknown role is rejected
at the input layer rather than reaching the enum column. Suspended users
remain invisible to non-admins and excluded by default, unless the expression
references suspendedAt.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* refactor: Collapse the duplicate suspended user predicate
The non-admin invariant and the default exclusion pushed the same clause for
non-admins in the default case. Both rules are now one predicate: suspended
users are visible to admins only, and then only on request.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* refactor: Drop the legacy parameters from the list_users MCP tool
The MCP surface has no backwards compatibility burden, so it takes the filter
DSL directly instead of the deprecated role and status parameters. This gives
the model date ranges, OR groups and name matching, which the old enum pair
could not express.
The field allowlist moves next to the other user filter helpers so the REST
schema and the tool share one definition rather than the tools directory
reaching into the routes.
Drops the unreachable Date member of FilterValue. Dates cross the wire as ISO
8601 strings, a Date instance fails every field kind, and zod cannot represent
it in the JSON Schema the MCP tool list is built from.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* revert: Retain legacy role/filter params in the list_users MCP tool for now
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Revert MCP changes
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Add heading numbering display preference for documents
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Fix isRemoteTransaction call for new signature on main
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Fix inTable detection for headings after a nested table
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* Move from deco to pseudoclass
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
* wip
* Center reorder cursors between sections, detect empty sections with CSS
* Deduplicate persisted sidebar section order
* fix: Stricter zod type
* Remove DraggableSection unit tests
* fix: Normalize path when keying rate limiters
The router matches paths case-insensitively and with an optional trailing
slash, so those variants each received their own quota. Collapse them onto
a single key at both registration and consumption.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* feedback
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Rate limit response headers and first-request accounting
Retry-After and RateLimit-Reset are both defined as a whole number of
seconds. Retry-After was sent as a fraction and RateLimit-Reset as a full
date string, neither of which a client can act on.
A route limiter is registered by middleware that runs after the point where
quota is consumed, so the first request to reach a path in each process was
never charged against it. Charge it at registration time instead.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* test: Cover rate limit headers and first request accounting
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* perf: Cache JS chunks on first use instead of precaching entire build
The service worker precached every JS chunk (~590 files) in the
background for every visitor. Chunks are content-hashed and immutable,
so a CacheFirst runtime route provides the same repeat-visit behavior
while only fetching chunks that are actually used.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
* perf: Do not register service worker on public share views
Anonymous share visitors gain nothing from the worker or the PWA
cache, shares always require the API. The server now exposes an
isShare flag in window.env and the client skips registration when
it is set.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
* feat: Unpin and context menu controls on pinned documents
- Adds an unpin control to document chips in the collapsed pinned view
- Adds the collapse toggle to collections, matching home
- Makes the Pin menu items toggles with a selected state
- Adds a document context menu to pinned cards and chips
- Stops the drag sensor swallowing clicks on the card unpin button
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Hide the collection pin toggle for a mixed selection
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* wip: Epic support
* fix: Unfurl GitLab epics and group work items
Group-scoped work items are parsed as project issues, producing a project
path of `groups/<group>` and a 404 from the issues API. Parse the namespace
around the `/-/` separator instead, and fetch group-scoped resources via the
epics API.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Truncate long mention labels instead of wrapping
A mention with a long unfurled title wrapped the pill onto several lines.
Cap it to a single line and elide the label, keeping icons and the trailing
identifier intact.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Build the project path only for project-scoped resources
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Opening the nested math editor moves focus, which dismisses the
suggestions menu. Restoring focus to the outer view re-entered the node
view's selection handling before it had finished, throwing "inner view
should not exist!".
Fixes OUTLINE-CLOUD-BZA
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
The modification loop advanced its cursor with node sizes read from the
slice, which describes the content before the change. When one step
replaces several sibling nodes the changeset emits a change per node,
each carrying the whole slice, so the later changes walked past the end
of the document and decoration building threw.
Measure each decorated node in the document being decorated instead.
Fixes OUTLINE-CLOUD-D19
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
The heading node bound its caret-sync handler to Mod-ArrowLeft, which
Prosemirror maps to Ctrl on Linux and Windows. The handler moved the
selection to the start of the heading, replacing the word-left movement
that Ctrl+Left performs everywhere else.
Bind Cmd rather than Mod, so the handler only runs for the shortcut it
was written for.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* Animate drafts count in sidebar
Adds a subtle pop animation when the drafts count appears or changes.
* Key drafts count animation on the displayed value
* fix: Sanitize the embed toolbar link and anchor embed url matchers
The "Open" link in an embed's bottom bar wrote the node's href attribute
into the DOM without passing it through sanitizeUrl, so a javascript: url
in that attribute ran on click.
Two embed matchers, and the regex built from a team's embed integration
settings, were not anchored, so a javascript: url that contained a
supported url further along still matched an embed and reached that link.
* fix: Only emit a list style the editor renders
The listStyle attribute is written into a list-style-type declaration.
Its validator returned a boolean rather than throwing, which Prosemirror
ignores, so any string reached the style attribute and a crafted value
appended further CSS declarations to the element.
* fix: Sanitize the image urls carried in a mention's unfurl attribute
The unfurl attribute holds a cached copy of the unfurl response on the
node, and is used whenever the store has no live entry for the url. Its
favicon and avatar urls were written to an img src unchanged, so a
crafted mention made every reader's browser request a chosen host.
* fix: Render a heading level and highlight color that cannot be used
Both attributes are used unchecked when the node is rendered. rgba()
throws for a color it cannot parse, and a level outside of 1-6 produces
an invalid tag name, so either one stopped the whole document rendering
in the browser and on the server. The heading level also reached a
repeat() in the Markdown serializer, unbounded.
Fall back when rendering rather than when reading, so that a value
written through collaborative editing, which does not run the attribute
validators, is covered too.
Focusing the editor can flush pending DOM changes, so the selection
captured before the focus call may no longer point at the current
document. Only restore it when the document is unchanged.
Fixes OUTLINE-CLOUD-CP6
A dynamic import can resolve to a chunk from a different build, throwing
"does not provide an export named", which was not recognized as a chunk
error. Share one stale chunk matcher between the lazy import retry, the
error boundary, and Sentry so all three treat it as recoverable.
Fixes OUTLINE-CLOUD-D1M
* fix: Uncaught error handling messages from the diagram editor
The diagram editor also posts plain text messages, such as "ready", which
were passed straight to JSON.parse and threw from the window listener.
- Ignore any message that is not a JSON object.
- Ignore messages when the editor window is not open. A blocked popup left
the window null, which matched the null source of unrelated messages.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Validate messages from the diagram editor against a schema
Replaces the message interface with a zod schema, so arrays and known
fields with unexpected types are rejected rather than trusted.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Correct open depths when unwrapping a single table cell on copy
The transformCopied prop replaced the slice content with the cell's content
but kept the original open depths, which still counted the removed table,
row, and cell levels. The resulting slice claimed to be open deeper than its
content, so any drag of a selection made inside a table cell threw in
dropPoint as the drop cursor walked into it.
Fixes OUTLINE-CLOUD-99J
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Unwrap single header cells on copy too
Header cells use the header_cell table role, so they never matched the
single-cell check and kept the table wrapper on copy.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
jsdom does not implement ResizeObserver, so a PDF attachment preview in a
publicly shared document threw from a React passive effect during HTML
rendering. Effect errors are not caught by the node view fallback, so the
uncaught exception took down the process.
Fixes OUTLINE-CLOUD-D14
The file name added to Content-Disposition was written into the header
unencoded whenever it fell inside Latin-1, so é, ü and ñ survived as raw
high bytes. Request signing hashes header values as UTF-8 while Node
writes them as Latin-1, giving the storage provider different bytes to
those that were signed, and the upload was rejected.
Pass an ASCII-only fallback so any such name is carried in the RFC 5987
filename* parameter instead. Browsers still read the original name from
there, so the extension is preserved.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Viewing the trash showed everything the whole workspace had deleted, which
is noisy for anyone looking for their own document. Default the view to the
items the current user deleted, and add user and date filters — matching the
shape of the search filters — to widen it again.
- Attribute a deleted subtree to the acting user. Deleting a document only
recorded the actor against the document itself, so nested pages kept
whoever last edited them and would have been hidden from their deleter.
- Move documents.deleted onto the filter DSL, exposing deletedById and
deletedAt. deletedById is mapped to the column that currently records the
deleting user, so adding a dedicated column later leaves the API unchanged.
- Lift the date filter duration map into shared, where search and the trash
both read it rather than keeping a copy each.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Moves mailparser to 3.9.15, which requests newer linkify-it and nodemailer
directly and makes two existing resolutions redundant. Adds a scoped
resolution to move deepmerge-ts to 8.x, and floats our own nodemailer range
so it dedupes to a single copy.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Replacing the download dialog with the export submenu lost the option to
include child documents, which defaulted to on. Restore it as the default
behavior for every format, and move the background export toast into the
model so all download paths raise it.
IconLibrary named-imported icons from the package barrels, which the Mermaid
extension also loads as whole icon packs. Sharing one copy of the barrel meant
every icon was retained and shipped on nearly every route. Importing each icon
from its own module leaves the barrels behind Mermaid's lazy icon pack loaders.
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: Stabilize signed attachment urls so caches can be reused
Every call to getSignedUrl produced a unique signature, so the same
attachment was downloaded again for each URL. On a public share the
first image was fetched twice at full size: once by the preload scanner
from the server-rendered HTML, and again when the client rendered the
document from the API response.
- Round the signing timestamp down to a window so repeated signatures of
the same key are identical. The window is capped at half the requested
lifetime, so a URL is always valid for at least half of expiresIn and
never outlives the lifetime it had before.
- Apply to all three signing paths: the S3 presigner, CloudFront, and
the JWT used by local storage.
- Sign the share page HTML with the same lifetime the API presenter
uses, so the two agree.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* test: Freeze time in signed url tests
The suites read the wall clock, so two calls could straddle a signing
window boundary and fail intermittently. Freeze the clock at a time
offset from a boundary, then advance it explicitly to cover both cases:
within a window the signature holds, across a boundary it rotates.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>