Skip to content

Give the paged organization list its own cache key - #157

Merged
vitramir merged 1 commit into
mainfrom
give-the-paged-list-its-own-key
Aug 28, 2026
Merged

Give the paged organization list its own cache key#157
vitramir merged 1 commit into
mainfrom
give-the-paged-list-its-own-key

Conversation

@vitramir

Copy link
Copy Markdown
Contributor

Opening Users and then Organizations blanks the console.

Both screens cached under ['organizations', 'list'], but they cache different shapes: OrganizationsListPage pages through and stores a flattened array, while UsersListPage and RegisterAppDialog each store a single response object. Whichever loaded first decided what the other read, so the organizations page mapped over a response object:

Error: (s.data ?? []).map is not a function

A render that throws takes the whole console down — the layout unmounts and the page goes blank, sidebar and all.

Found from the trace of console navigation › opens every platform sidebar section, which walks Users then Organizations and so hits the collision every time; that walk is the regression guard.

Two screens cached different things under one key: the organizations
list flattens every page into an array, while the users list and the app
dialog each keep a single response. Whichever ran first decided what the
other one read, so opening Users and then Organizations mapped over a
response object and threw -- and a render that throws takes the console
with it, leaving a blank page where the sidebar had been.
@vitramir
vitramir merged commit 127d25c into main Aug 28, 2026
1 of 2 checks passed
@vitramir
vitramir deleted the give-the-paged-list-its-own-key branch August 28, 2026 21: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