store-data-structures

Use a simple array for list data (e.g. benchmarkList: ListItem[]) and a Record<string, Detail> map for detail data. The map caches multiple detail pages simultaneously and supports per-item loading states via a loadingIds array.

Define a discriminated union of action types and a pure reducer using Immer's produce. Expose internal dispatch methods on the slice that run the reducer and call set only when the map actually changed, keeping mutations testable.

No. List item types should be standalone subsets that exclude heavy fields like content, rubrics, or editor state. Extending the detail type pulls those heavy fields back into list payloads, slowing list rendering.

Use an array for list display data that refreshes as a whole without per-item mutation. Use a Record map for detail data when you need multi-entity caching, optimistic updates, and per-item loading states.

No. Stores should import types from a shared types package such as @lobechat/types, not from the database layer. This keeps client state decoupled from persistence schemas and avoids leaking server-only fields.