Repo-owner report, 2026-05-26: "the cells that are links should be styled as links."
In the list table, ForeignKey cells (e.g. a "loan package" column rendering Test Loan Package 7 (...)) render as plain black text. They represent a link to another object and should be styled as links (and, ideally, navigate to that object's detail).
Current behaviour
FieldValueView → renderValue renders the FK wire value { id, label } as plain text. No visual link affordance.
What's needed
- Styling: FK cells render with link styling (e.g.
text-blue-600 hover:underline) so it's visually obvious they're navigable — matching Django admin's list_display FK links.
- Navigation (depends on metadata): to make the FK cell a real
<Link> to /<app>/<model>/<id>, the column descriptor must carry the FK target (to: {app_label, model_name}). Today the FK value is only {id, label} (no target model). So:
- Backend: include the FK target on the list column descriptor (the
list_filter FK descriptor already has to: — mirror it on columns[] for FK fields).
- Frontend: when a column is an FK and the row value is
{id, label}, render <Link to={/${to.app_label}/${to.model_name}/${value.id}}> styled as a link.
- The first
list_display column (or list_display_links) should link to the row's own detail (Django's behaviour) — also styled as a link, not just a click target.
Acceptance
FK cells in the list render as styled links; clicking one navigates to the related object's detail (when the column metadata carries the FK target).
Priority
P1 / v0.1 / Frontend (styling) + a small Backend add (FK target on column descriptor). Part of the list-UX parity set with #177 / #181 / #182.
Repo-owner report, 2026-05-26: "the cells that are links should be styled as links."
In the list table, ForeignKey cells (e.g. a "loan package" column rendering
Test Loan Package 7 (...)) render as plain black text. They represent a link to another object and should be styled as links (and, ideally, navigate to that object's detail).Current behaviour
FieldValueView→renderValuerenders the FK wire value{ id, label }as plain text. No visual link affordance.What's needed
text-blue-600 hover:underline) so it's visually obvious they're navigable — matching Django admin'slist_displayFK links.<Link>to/<app>/<model>/<id>, the column descriptor must carry the FK target (to: {app_label, model_name}). Today the FK value is only{id, label}(no target model). So:list_filterFK descriptor already hasto:— mirror it oncolumns[]for FK fields).{id, label}, render<Link to={/${to.app_label}/${to.model_name}/${value.id}}>styled as a link.list_displaycolumn (orlist_display_links) should link to the row's own detail (Django's behaviour) — also styled as a link, not just a click target.Acceptance
FK cells in the list render as styled links; clicking one navigates to the related object's detail (when the column metadata carries the FK target).
Priority
P1 / v0.1 / Frontend (styling) + a small Backend add (FK target on column descriptor). Part of the list-UX parity set with #177 / #181 / #182.