chore(release): v1.4.8 — standard ModelAdmin.actions on the detail page (#614)

Closes #603 revised. Patch — dep bump + client cleanup, no behaviour change beyond 'actions actually show up.'

Author: MartinCastroAlvarez

examples/fintech/admin.py

@@ -23,6 +23,38 @@ class TransactionAdmin(admin.ModelAdmin):
     date_hierarchy = "posted_at"
     autocomplete_fields = ("account",)
     readonly_fields = ("reference",)
+    # Stock Django admin actions (`@admin.action`). They surface on the
+    # changelist (multi-pk runs) AND the SPA's detail page header
+    # (single-pk runs) — no `django-object-actions` mixin, no
+    # `change_actions = [...]` redeclaration. One source of truth for
+    # everything the consumer wants to expose as an action.
+    actions = ("mark_reconciled", "recompute_reference")
+
+    @admin.action(description="Mark as reconciled")
+    def mark_reconciled(self, request, queryset):
+        """Tag every row in the queryset as reconciled.
+
+        Demo no-op: the model has no `reconciled` flag yet — this
+        exists so the SPA's detail page has a stock-Django-admin
+        action to render. A real ModelAdmin would update the row
+        and message the user.
+        """
+        count = queryset.count()
+        self.message_user(request, f"Marked {count} transaction(s) as reconciled.")
+
+    @admin.action(description="Recompute reference")
+    def recompute_reference(self, request, queryset):
+        """Roll the ``reference`` field on each row in the queryset.
+
+        Demo: bumps ``reference`` to ``TXN-RECOMP-<stamp>-<i>`` so the
+        operator can see the action ran end-to-end on the SPA.
+        """
+        from datetime import datetime, timezone as tz
+        stamp = datetime.now(tz.utc).strftime("%Y%m%d%H%M%S")
+        for i, row in enumerate(queryset):
+            row.reference = f"TXN-RECOMP-{stamp}-{i:02d}"
+            row.save(update_fields=["reference"])
+        self.message_user(request, f"Recomputed reference on {queryset.count()} row(s).")
 
 
 @admin.register(Statement)

frontend/packages/api/src/client.ts

@@ -18,7 +18,6 @@ import type {
   HistoryResponse,
   ListResponse,
   LoginResponse,
-  ObjectActionRunResponse,
   RecentActionsResponse,
   RegistryResponse,
   UpdatePayload,
@@ -336,25 +335,13 @@ export class ApiClient {
     );
   }
 
-  /**
-   * Run one object-level change-page action (#236) against a single
-   * object (`POST <app>/<model>/<pk>/action/<name>/`). The backend
-   * re-resolves `name` through the admin's permitted `get_change_actions`
-   * set — the SPA name is never trusted as a callable lookup. CSRF is
-   * sent like other unsafe calls. Returns `{ok, message?, redirect?}`.
-   */
-  runObjectAction(
-    appLabel: string,
-    modelName: string,
-    pk: string | number,
-    name: string,
-  ): Promise<ObjectActionRunResponse> {
-    return this.request<ObjectActionRunResponse>(
-      'POST',
-      `${appLabel}/${modelName}/${pk}/action/${name}/`,
-      {},
-    );
-  }
+  // `runObjectAction` is intentionally not on the HTTP client anymore
+  // (v1.4.8 / #603 revised). The dedicated `/<pk>/action/<name>/`
+  // endpoint was removed in api 1.0.5 — detail-page actions now go
+  // through `runAction(name, [pk])` against the existing changelist
+  // runner. The legacy `runObjectAction` helper still exists in
+  // `@dar/data`'s mutations.ts, but it delegates to `runAction`
+  // internally rather than hitting a separate endpoint.
 
   /**
    * Typeahead for a high-cardinality FK picker (contract §3.2). The

frontend/packages/data/src/mutations.ts

@@ -63,7 +63,32 @@ export function fetchDeletePreview(args: DeletePreviewArgs): Promise<DeletePrevi
   return args.client.deletePreview(args.appLabel, args.modelName, args.pk);
 }
 
-/** Run one object-level change-page action (#236). */
-export function runObjectAction(args: RunObjectActionArgs): Promise<ObjectActionRunResponse> {
-  return args.client.runObjectAction(args.appLabel, args.modelName, args.pk, args.name);
+/**
+ * Run one detail-page action on a single object.
+ *
+ * Reuses the existing changelist actions runner (#603 revised, v1.4.8):
+ * `data.object_actions` on the detail response is now sourced from the
+ * standard `ModelAdmin.actions` — same descriptor builder as the list
+ * response — so the SPA reuses the same `POST <app>/<model>/actions/
+ * <name>/` runner with `pks=[<this pk>]`. No dedicated per-object
+ * endpoint, no `django-object-actions` integration.
+ *
+ * Translates the changelist response shape (`{executed, messages,
+ * redirect?}`) into the legacy `{ok, message?, redirect?}` callers
+ * already consume — same external contract, simpler wiring.
+ */
+export async function runObjectAction(
+  args: RunObjectActionArgs,
+): Promise<ObjectActionRunResponse> {
+  const res = await args.client.runAction(args.appLabel, args.modelName, args.name, [args.pk]);
+  // First `message_user` message becomes the legacy `message` field —
+  // the SPA toasts it on success. Additional messages stay reachable
+  // via the full ActionRunResponse if a caller wants to upgrade off
+  // the legacy shape.
+  const message = res.messages && res.messages.length > 0 ? res.messages[0]?.message : undefined;
+  return {
+    ok: res.executed,
+    ...(message !== undefined ? { message } : {}),
+    ...(res.redirect !== undefined ? { redirect: res.redirect } : {}),
+  };
 }

poetry.lock

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "django-admin-react"
-version = "1.4.7"
+version = "1.4.8"
 description = "A drop-in React single-page admin for Django, driven entirely by ModelAdmin."
 authors = ["django-admin-react contributors"]
 license = "MIT"
@@ -49,7 +49,7 @@ django = ">=5.0,<7.0"
 # React SPA super-layer over `django-admin-rest-api`. The package's URLs
 # are included by `django_admin_react.urls`, and consumers add
 # `"django_admin_rest_api"` to `INSTALLED_APPS` alongside this package.
-django-admin-rest-api = "^1.0.4"
+django-admin-rest-api = "^1.0.5"
 # `django-admin-mcp-api` — MCP-protocol adapter over the same REST API
 # so agents reach the SAME `ModelAdmin`-driven surface. Wire-protocol-only
 # layer; adds NO new functionality, permissions, or validation.