Lists: card, grid and ERD view modes #52

Activity

1. Adron

   added

   parityClosing a gap against interlinedlist.comClosing a gap against interlinedlist.com

   P2Completeness / settings surfaceCompleteness / settings surface

   area:listsListsLists

   on Sep 15, 2026
2. Adron

   added a parent issue on Sep 15, 2026

   • Lists parity gaps: GitHub-backed lists, saved views, view modes and collaborative editing #49
3. Adron commented on Sep 16, 2026

   

   Adron

   on Sep 16, 2026

   MemberAuthor

   More actions

   Blocked on a question — this issue's core assumption is not supported by the live API

   Picked this up after #51 (saved views) landed, and stopped. #51 needed the saved-view config shape
   confirmed live, so I created a view on the test account and probed it. That probe contradicts what
   this issue assumes.

   config.mode only ever stores records. I sent each of these as config.mode on
   PUT /api/lists/{id}/views/{viewId}:

   cards, card, grid, table, erd, diagram, board, gallery, kanban, list

   Every one came back as "mode": "records", with HTTP 200 and no error. The server silently
   rewrites an unrecognised value rather than rejecting it. (density behaves the same way — it
   accepted comfortable and compact, and quietly rewrote cozy and spacious to comfortable.)

   So a saved view cannot currently record "this list renders as cards / a grid / an ERD", which is
   what this issue is asking Android to build.

   What I need from you

   1. Where does the web store the view mode? Three possibilities:
      • (a) It is client-side only — the web keeps card/grid/ERD in local state or localStorage and
        never persists it per-view. If so, this issue is still buildable, but as a device-local
        preference, and it will not follow the user between web and Android. Confirm that is
        acceptable and I will build it that way.
      • (b) It lives under a different config key that I did not guess. Tell me the key and the
        accepted values and I will implement it properly.
      • (c) It is gated on something the test account (messenger, a subscriber) lacks.
   2. What are the real accepted values for config.mode? records is the only one I could
      observe. If the set is larger, I need the exact strings — guessing is what produced the silent
      rewrites above.
   3. Is the ERD view meaningful on a phone? An entity-relationship diagram of a list's connections
      is the one of the three that may not survive the form factor. If you want it, I would rather
      design it deliberately than shrink the web's rendering.

   What is already in place

   #51 built the client half so nothing is lost whichever answer comes back: ListViewConfig preserves
   config keys the client does not model through a full round-trip, and exposes storedMode so the
   server's actual value is always visible. When the mechanism is confirmed, this issue is mostly
   extending one enum plus the three renderers.

   Leaving this open and unimplemented until the above is settled.