django-admin-react 0.2.0a7__tar.gz → 1.0.0__tar.gz

{django_admin_react-0.2.0a7 → django_admin_react-1.0.0}/PKG-INFO

@@ -1,12 +1,12 @@
 Metadata-Version: 2.3
 Name: django-admin-react
-Version: 0.2.0a7
+Version: 1.0.0
 Summary: A drop-in React single-page admin for Django, driven entirely by ModelAdmin.
 License: MIT
 Keywords: django,admin,react,spa,tailwind
 Author: django-admin-react contributors
 Requires-Python: >=3.10,<4.0
-Classifier: Development Status :: 2 - Pre-Alpha
+Classifier: Development Status :: 4 - Beta
 Classifier: Environment :: Web Environment
 Classifier: Framework :: Django
 Classifier: Framework :: Django :: 5.0
@@ -24,6 +24,8 @@ Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: Internet :: WWW/HTTP :: Site Management
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Requires-Dist: django (>=5.0,<7.0)
+Requires-Dist: django-admin-mcp-api (>=0.1.0a0,<0.2.0)
+Requires-Dist: django-admin-rest-api (>=1.0.1,<2.0.0)
 Project-URL: Documentation, https://github.com/MartinCastroAlvarez/django-admin-react#readme
 Project-URL: Homepage, https://github.com/MartinCastroAlvarez/django-admin-react
 Project-URL: Repository, https://github.com/MartinCastroAlvarez/django-admin-react
@@ -35,11 +37,42 @@ A drop-in **React single-page admin** for any Django 5+ project. Same
 `pip install`, same `INSTALLED_APPS`, same `urls.py include()` — and
 your `ModelAdmin` classes drive everything. No React code on your side.
 
-> **Pre-alpha.** Available on PyPI as an alpha. Pin tightly; expect
-> breaking changes between alpha releases. Track progress on the
+```python
+# settings.py
+INSTALLED_APPS = [
+    # ...
+    "django.contrib.admin",
+    "django_admin_rest_api",   # the JSON REST API (sibling package — pulled in as a dependency)
+    "django_admin_react",      # this package — the React SPA on top of it
+]
+
+# urls.py
+urlpatterns = [
+    path("admin/",       admin.site.urls),
+    path("admin-react/", include("django_admin_react.urls")),  # SPA + its API include
+]
+```
+
+> **Beta — v1.0.0.** Available on PyPI; the SPA + the API
+> ([`django-admin-rest-api`](https://pypi.org/project/django-admin-rest-api/))
+> + the MCP adapter
+> ([`django-admin-mcp-api`](https://pypi.org/project/django-admin-mcp-api/))
+> all share the v1 wire contract. Track progress on the
 > [Project board](https://github.com/users/MartinCastroAlvarez/projects/3)
 > and the [Issues list](https://github.com/MartinCastroAlvarez/django-admin-react/issues).
 
+## Three repos, one product
+
+The project is split into three independently-published, cross-referenced repos so each piece can be consumed on its own merits:
+
+| Repo | PyPI | Role |
+|---|---|---|
+| **[`django-admin-rest-api`](https://github.com/MartinCastroAlvarez/django-admin-api)** | [`django-admin-rest-api`](https://pypi.org/project/django-admin-rest-api/) | The JSON REST API for the Django admin — same permissions, same `ModelAdmin`, no new features. The wire surface. |
+| **`django-admin-react`** *(this repo)* | [`django-admin-react`](https://pypi.org/project/django-admin-react/) | The React SPA frontend. A **super-layer** that depends on `django-admin-rest-api` for every wire call. |
+| **[`django-admin-mcp-api`](https://github.com/MartinCastroAlvarez/django-admin-mcp)** | [`django-admin-mcp-api`](https://pypi.org/project/django-admin-mcp-api/) | Wire-protocol-only **MCP** adapter (call, manifest, …) over `django-admin-rest-api` — lets agents reach the same `ModelAdmin`-driven REST surface, no new functionality / permissions / validation. |
+
+The wire contract itself lives in the **API repo** (`docs/api-contract.md` there). This README is about the SPA. The migration from "self-contained" to the 3-repo split is tracked in [META #544](https://github.com/MartinCastroAlvarez/django-admin-react/issues/544).
+
 ---
 
 ## Why django-admin-react
@@ -77,8 +110,8 @@ permissions at runtime from `GET /api/v1/registry/`. Add a new
 
 Real captures of the **django-admin-react SPA** rendering the bundled
 `examples/` apps — driven entirely by each app's `ModelAdmin`.
-Regenerate any time with `scripts/screenshots.sh` (Playwright against a
-throwaway example server).
+Captured **manually** against a local dev server (no Playwright / Cypress /
+e2e tooling required).
 
 | Sign in (package login)                            | Registry / home                                       |
 | -------------------------------------------------- | ----------------------------------------------------- |
@@ -103,34 +136,16 @@ emails, account numbers, or PII).
 pip install django-admin-react
 ```
 
-```python
-# settings.py
-INSTALLED_APPS = [
-    "django.contrib.admin",
-    "django.contrib.auth",
-    "django.contrib.contenttypes",
-    "django.contrib.sessions",
-    "django.contrib.messages",
-    "django.contrib.staticfiles",
-    "django_admin_react",   # ← add this
-    # ... your own apps
-]
-```
-
-```python
-# urls.py
-from django.urls import include, path
+This pulls in the JSON API ([`django-admin-rest-api`](https://pypi.org/project/django-admin-rest-api/))
+and the MCP adapter ([`django-admin-mcp-api`](https://pypi.org/project/django-admin-mcp-api/))
+as transitive dependencies. The **two-line `INSTALLED_APPS` + one-line
+URL include** at the top of this README is the *entire* integration.
+Mount at any prefix you like — `/admin-react/`, `/staff/`,
+`/back-office/` — just don't collide with `django.contrib.admin`'s
+own mount.
 
-urlpatterns = [
-    path("admin/", include("django_admin_react.urls")),
-    # any prefix is fine:
-    # path("admin-react/", include("django_admin_react.urls")),
-    # path("staff/",       include("django_admin_react.urls")),
-]
-```
-
-That is the entire integration. Log in as a staff user → modern,
-Tailwind-styled SPA driven by your existing `ModelAdmin` classes.
+Log in as a staff user → modern, Tailwind-styled SPA driven by your
+existing `ModelAdmin` classes.
 
 The wheel ships the **pre-built React bundle**. You do **not** need
 Node, pnpm, or any frontend toolchain to install or run.
@@ -142,35 +157,60 @@ All settings are optional. Defaults shown:
 ```python
 DJANGO_ADMIN_REACT = {
     "ADMIN_SITE": "django.contrib.admin.site",   # dotted path to AdminSite instance
-    "DEFAULT_PAGE_SIZE": 25,
+    "DEFAULT_PAGE_SIZE": 25,    # fallback only; the list page size derives
+                                # from ModelAdmin.list_per_page (Django parity).
     "MAX_PAGE_SIZE": 200,
     "ENABLE_PROFILING": False,
 
-    # Branding — rendered server-side into the SPA shell, so the
-    # consumer's title + favicon are present on first paint (no FOUC).
-    "BRAND_TITLE": None,        # str | None — sidebar header + browser tab.
-    "BRAND_LOGO_URL": None,     # str | None — used as the favicon and
-                                # the sidebar logo. Absolute URL or a
-                                # path under your STATIC_URL.
+    # Branding — all optional. The defaults derive from your AdminSite
+    # (site_header / site_title / site_logo), so if you already branded
+    # the HTML admin you need nothing here. Rendered server-side into the
+    # SPA shell, so title + favicon are present on first paint (no FOUC).
+    "BRAND_TITLE": None,        # str | None — override for BOTH brand strings.
+    "BRAND_LOGO_URL": None,     # str | None — favicon + sidebar logo;
+                                # falls back to AdminSite.site_logo. Absolute
+                                # URL or a path under your STATIC_URL.
     "PRIMARY_COLOR": "#2563eb", # accent for primary buttons, links, and
                                 # active states. Hex only (validated);
                                 # injected as the --dar-primary CSS var, so
                                 # rebranding needs no React rebuild.
+
+    # Auth + API mount
+    "REACT_LOGIN": True,        # bool — React-rendered login is the default;
+                                # the SPA shell is served to anonymous users
+                                # and posts to /api/v1/login/. Set False to
+                                # opt back into the legacy admin HTML login.
+    "API_URL_PREFIX": None,     # str | None — point the SPA at a separately-
+                                # mounted django-admin-rest-api (e.g.
+                                # "/api/api/v1/"). Default None keeps the
+                                # inline include the package ships today.
 }
 ```
 
 #### Branding (`BRAND_TITLE` + `BRAND_LOGO_URL`)
 
-Both default to `None`. Resolution order for the title:
+Both default to `None` and **derive from your `AdminSite`**, mirroring
+Django admin — so if you already customised the HTML admin's branding,
+you need no settings here at all.
+
+**Sidebar header** resolution:
 
 1. `DJANGO_ADMIN_REACT["BRAND_TITLE"]` — explicit override.
-2. `<your AdminSite>.site_header` — if you already set `site_header`
-   on a custom `AdminSite`, the SPA reuses it automatically. No need
-   to repeat yourself.
+2. `<your AdminSite>.site_header` — reused automatically.
 3. `"Django Admin"` — last-resort fallback.
 
+**Browser-tab `<title>`** resolution (Django uses `site_title` for the
+tab, `site_header` for the on-page header):
+
+1. `DJANGO_ADMIN_REACT["BRAND_TITLE"]` — explicit override.
+2. `<your AdminSite>.site_title` — Django's tab-title source.
+3. `<your AdminSite>.site_header` — fallback.
+4. `"Django Admin"` — last-resort fallback.
+
 `BRAND_LOGO_URL` accepts either an absolute URL or a path the browser
-can resolve under your `STATIC_URL`. It is used both as the favicon
+can resolve under your `STATIC_URL`. When unset, a `site_logo` attribute
+on your `AdminSite` is used (Django has no logo by default, so set it as
+a constant on your custom site). It is used both as the favicon
 (`<link rel="icon">` in the SPA shell) and as the small logo next to
 the brand title in the sidebar.
 
@@ -447,8 +487,9 @@ register_field_type(MoneyField, vocab_type="decimal")
 # code required.
 ```
 
-For coining a brand-new `vocab_type` (with a matching SPA widget)
-see [`docs/extensions.md`](docs/extensions.md).
+Coining a brand-new `vocab_type` (with a matching SPA widget) is an
+**API-repo** concern — open the issue at
+[`MartinCastroAlvarez/django-admin-api`](https://github.com/MartinCastroAlvarez/django-admin-api).
 
 ### Pre-built `get_*` overrides still work
 
@@ -495,7 +536,6 @@ and the [project board](https://github.com/users/MartinCastroAlvarez/projects/3)
 ✅ = shipped in the current alpha. 🟡 = not yet built (tracked). This
 column is the **backend** capability only — for which surfaces the React
 UI renders today, see the [frontend tracker (#160)](https://github.com/MartinCastroAlvarez/django-admin-react/issues/160).
-[`ACCEPTANCE.md`](ACCEPTANCE.md) carries the full criterion-by-criterion list.
 
 ---
 
@@ -520,8 +560,9 @@ frontend, a script).
 
 Every endpoint is **staff-only by default** (or whatever
 `AdminSite.has_permission` returns), CSRF-required on unsafe
-methods, and emits `Cache-Control: no-store`. Full wire contract:
-[`docs/api-contract.md`](docs/api-contract.md).
+methods, and emits `Cache-Control: no-store`. Full wire contract
+lives in the API repo:
+[`MartinCastroAlvarez/django-admin-api`](https://github.com/MartinCastroAlvarez/django-admin-api).
 
 ---
 
@@ -585,6 +626,10 @@ See [`SECURITY.md`](SECURITY.md). Do **not** open a public issue.
 
 ## Contributing
 
-Humans and AI agents both welcome. Start with
-[`CONTRIBUTING.md`](CONTRIBUTING.md).
+Open an [Issue](https://github.com/MartinCastroAlvarez/django-admin-react/issues/new)
+or a [Discussion](https://github.com/MartinCastroAlvarez/django-admin-react/discussions)
+before sending a PR for anything non-trivial. **API-side contributions** (any
+`/api/v1/...` endpoint, the wire contract, permission gates, serializer
+denylist) go to [`MartinCastroAlvarez/django-admin-api`](https://github.com/MartinCastroAlvarez/django-admin-api)
+— this repo owns only the **React SPA super-layer** on top.
 

{django_admin_react-0.2.0a7 → django_admin_react-1.0.0}/README.md

@@ -4,11 +4,42 @@ A drop-in **React single-page admin** for any Django 5+ project. Same
 `pip install`, same `INSTALLED_APPS`, same `urls.py include()` — and
 your `ModelAdmin` classes drive everything. No React code on your side.
 
-> **Pre-alpha.** Available on PyPI as an alpha. Pin tightly; expect
-> breaking changes between alpha releases. Track progress on the
+```python
+# settings.py
+INSTALLED_APPS = [
+    # ...
+    "django.contrib.admin",
+    "django_admin_rest_api",   # the JSON REST API (sibling package — pulled in as a dependency)
+    "django_admin_react",      # this package — the React SPA on top of it
+]
+
+# urls.py
+urlpatterns = [
+    path("admin/",       admin.site.urls),
+    path("admin-react/", include("django_admin_react.urls")),  # SPA + its API include
+]
+```
+
+> **Beta — v1.0.0.** Available on PyPI; the SPA + the API
+> ([`django-admin-rest-api`](https://pypi.org/project/django-admin-rest-api/))
+> + the MCP adapter
+> ([`django-admin-mcp-api`](https://pypi.org/project/django-admin-mcp-api/))
+> all share the v1 wire contract. Track progress on the
 > [Project board](https://github.com/users/MartinCastroAlvarez/projects/3)
 > and the [Issues list](https://github.com/MartinCastroAlvarez/django-admin-react/issues).
 
+## Three repos, one product
+
+The project is split into three independently-published, cross-referenced repos so each piece can be consumed on its own merits:
+
+| Repo | PyPI | Role |
+|---|---|---|
+| **[`django-admin-rest-api`](https://github.com/MartinCastroAlvarez/django-admin-api)** | [`django-admin-rest-api`](https://pypi.org/project/django-admin-rest-api/) | The JSON REST API for the Django admin — same permissions, same `ModelAdmin`, no new features. The wire surface. |
+| **`django-admin-react`** *(this repo)* | [`django-admin-react`](https://pypi.org/project/django-admin-react/) | The React SPA frontend. A **super-layer** that depends on `django-admin-rest-api` for every wire call. |
+| **[`django-admin-mcp-api`](https://github.com/MartinCastroAlvarez/django-admin-mcp)** | [`django-admin-mcp-api`](https://pypi.org/project/django-admin-mcp-api/) | Wire-protocol-only **MCP** adapter (call, manifest, …) over `django-admin-rest-api` — lets agents reach the same `ModelAdmin`-driven REST surface, no new functionality / permissions / validation. |
+
+The wire contract itself lives in the **API repo** (`docs/api-contract.md` there). This README is about the SPA. The migration from "self-contained" to the 3-repo split is tracked in [META #544](https://github.com/MartinCastroAlvarez/django-admin-react/issues/544).
+
 ---
 
 ## Why django-admin-react
@@ -46,8 +77,8 @@ permissions at runtime from `GET /api/v1/registry/`. Add a new
 
 Real captures of the **django-admin-react SPA** rendering the bundled
 `examples/` apps — driven entirely by each app's `ModelAdmin`.
-Regenerate any time with `scripts/screenshots.sh` (Playwright against a
-throwaway example server).
+Captured **manually** against a local dev server (no Playwright / Cypress /
+e2e tooling required).
 
 | Sign in (package login)                            | Registry / home                                       |
 | -------------------------------------------------- | ----------------------------------------------------- |
@@ -72,34 +103,16 @@ emails, account numbers, or PII).
 pip install django-admin-react
 ```
 
-```python
-# settings.py
-INSTALLED_APPS = [
-    "django.contrib.admin",
-    "django.contrib.auth",
-    "django.contrib.contenttypes",
-    "django.contrib.sessions",
-    "django.contrib.messages",
-    "django.contrib.staticfiles",
-    "django_admin_react",   # ← add this
-    # ... your own apps
-]
-```
-
-```python
-# urls.py
-from django.urls import include, path
+This pulls in the JSON API ([`django-admin-rest-api`](https://pypi.org/project/django-admin-rest-api/))
+and the MCP adapter ([`django-admin-mcp-api`](https://pypi.org/project/django-admin-mcp-api/))
+as transitive dependencies. The **two-line `INSTALLED_APPS` + one-line
+URL include** at the top of this README is the *entire* integration.
+Mount at any prefix you like — `/admin-react/`, `/staff/`,
+`/back-office/` — just don't collide with `django.contrib.admin`'s
+own mount.
 
-urlpatterns = [
-    path("admin/", include("django_admin_react.urls")),
-    # any prefix is fine:
-    # path("admin-react/", include("django_admin_react.urls")),
-    # path("staff/",       include("django_admin_react.urls")),
-]
-```
-
-That is the entire integration. Log in as a staff user → modern,
-Tailwind-styled SPA driven by your existing `ModelAdmin` classes.
+Log in as a staff user → modern, Tailwind-styled SPA driven by your
+existing `ModelAdmin` classes.
 
 The wheel ships the **pre-built React bundle**. You do **not** need
 Node, pnpm, or any frontend toolchain to install or run.
@@ -111,35 +124,60 @@ All settings are optional. Defaults shown:
 ```python
 DJANGO_ADMIN_REACT = {
     "ADMIN_SITE": "django.contrib.admin.site",   # dotted path to AdminSite instance
-    "DEFAULT_PAGE_SIZE": 25,
+    "DEFAULT_PAGE_SIZE": 25,    # fallback only; the list page size derives
+                                # from ModelAdmin.list_per_page (Django parity).
     "MAX_PAGE_SIZE": 200,
     "ENABLE_PROFILING": False,
 
-    # Branding — rendered server-side into the SPA shell, so the
-    # consumer's title + favicon are present on first paint (no FOUC).
-    "BRAND_TITLE": None,        # str | None — sidebar header + browser tab.
-    "BRAND_LOGO_URL": None,     # str | None — used as the favicon and
-                                # the sidebar logo. Absolute URL or a
-                                # path under your STATIC_URL.
+    # Branding — all optional. The defaults derive from your AdminSite
+    # (site_header / site_title / site_logo), so if you already branded
+    # the HTML admin you need nothing here. Rendered server-side into the
+    # SPA shell, so title + favicon are present on first paint (no FOUC).
+    "BRAND_TITLE": None,        # str | None — override for BOTH brand strings.
+    "BRAND_LOGO_URL": None,     # str | None — favicon + sidebar logo;
+                                # falls back to AdminSite.site_logo. Absolute
+                                # URL or a path under your STATIC_URL.
     "PRIMARY_COLOR": "#2563eb", # accent for primary buttons, links, and
                                 # active states. Hex only (validated);
                                 # injected as the --dar-primary CSS var, so
                                 # rebranding needs no React rebuild.
+
+    # Auth + API mount
+    "REACT_LOGIN": True,        # bool — React-rendered login is the default;
+                                # the SPA shell is served to anonymous users
+                                # and posts to /api/v1/login/. Set False to
+                                # opt back into the legacy admin HTML login.
+    "API_URL_PREFIX": None,     # str | None — point the SPA at a separately-
+                                # mounted django-admin-rest-api (e.g.
+                                # "/api/api/v1/"). Default None keeps the
+                                # inline include the package ships today.
 }
 ```
 
 #### Branding (`BRAND_TITLE` + `BRAND_LOGO_URL`)
 
-Both default to `None`. Resolution order for the title:
+Both default to `None` and **derive from your `AdminSite`**, mirroring
+Django admin — so if you already customised the HTML admin's branding,
+you need no settings here at all.
+
+**Sidebar header** resolution:
 
 1. `DJANGO_ADMIN_REACT["BRAND_TITLE"]` — explicit override.
-2. `<your AdminSite>.site_header` — if you already set `site_header`
-   on a custom `AdminSite`, the SPA reuses it automatically. No need
-   to repeat yourself.
+2. `<your AdminSite>.site_header` — reused automatically.
 3. `"Django Admin"` — last-resort fallback.
 
+**Browser-tab `<title>`** resolution (Django uses `site_title` for the
+tab, `site_header` for the on-page header):
+
+1. `DJANGO_ADMIN_REACT["BRAND_TITLE"]` — explicit override.
+2. `<your AdminSite>.site_title` — Django's tab-title source.
+3. `<your AdminSite>.site_header` — fallback.
+4. `"Django Admin"` — last-resort fallback.
+
 `BRAND_LOGO_URL` accepts either an absolute URL or a path the browser
-can resolve under your `STATIC_URL`. It is used both as the favicon
+can resolve under your `STATIC_URL`. When unset, a `site_logo` attribute
+on your `AdminSite` is used (Django has no logo by default, so set it as
+a constant on your custom site). It is used both as the favicon
 (`<link rel="icon">` in the SPA shell) and as the small logo next to
 the brand title in the sidebar.
 
@@ -416,8 +454,9 @@ register_field_type(MoneyField, vocab_type="decimal")
 # code required.
 ```
 
-For coining a brand-new `vocab_type` (with a matching SPA widget)
-see [`docs/extensions.md`](docs/extensions.md).
+Coining a brand-new `vocab_type` (with a matching SPA widget) is an
+**API-repo** concern — open the issue at
+[`MartinCastroAlvarez/django-admin-api`](https://github.com/MartinCastroAlvarez/django-admin-api).
 
 ### Pre-built `get_*` overrides still work
 
@@ -464,7 +503,6 @@ and the [project board](https://github.com/users/MartinCastroAlvarez/projects/3)
 ✅ = shipped in the current alpha. 🟡 = not yet built (tracked). This
 column is the **backend** capability only — for which surfaces the React
 UI renders today, see the [frontend tracker (#160)](https://github.com/MartinCastroAlvarez/django-admin-react/issues/160).
-[`ACCEPTANCE.md`](ACCEPTANCE.md) carries the full criterion-by-criterion list.
 
 ---
 
@@ -489,8 +527,9 @@ frontend, a script).
 
 Every endpoint is **staff-only by default** (or whatever
 `AdminSite.has_permission` returns), CSRF-required on unsafe
-methods, and emits `Cache-Control: no-store`. Full wire contract:
-[`docs/api-contract.md`](docs/api-contract.md).
+methods, and emits `Cache-Control: no-store`. Full wire contract
+lives in the API repo:
+[`MartinCastroAlvarez/django-admin-api`](https://github.com/MartinCastroAlvarez/django-admin-api).
 
 ---
 
@@ -554,5 +593,9 @@ See [`SECURITY.md`](SECURITY.md). Do **not** open a public issue.
 
 ## Contributing
 
-Humans and AI agents both welcome. Start with
-[`CONTRIBUTING.md`](CONTRIBUTING.md).
+Open an [Issue](https://github.com/MartinCastroAlvarez/django-admin-react/issues/new)
+or a [Discussion](https://github.com/MartinCastroAlvarez/django-admin-react/discussions)
+before sending a PR for anything non-trivial. **API-side contributions** (any
+`/api/v1/...` endpoint, the wire contract, permission gates, serializer
+denylist) go to [`MartinCastroAlvarez/django-admin-api`](https://github.com/MartinCastroAlvarez/django-admin-api)
+— this repo owns only the **React SPA super-layer** on top.

{django_admin_react-0.2.0a7 → django_admin_react-1.0.0}/django_admin_react/audit.py

@@ -17,6 +17,8 @@ Public surface:
 
 - :func:`object_log_entries` — the ``LogEntry`` queryset for one object,
   newest-first, with the acting user pre-fetched.
+- :func:`recent_actions_for_user` — the most recent ``LogEntry`` rows for
+  one user (the index "Recent actions" panel), newest-first.
 """
 
 from __future__ import annotations
@@ -40,3 +42,17 @@ def object_log_entries(obj: Model) -> QuerySet[LogEntry]:
         .select_related("user")
         .order_by("-action_time")
     )
+
+
+def recent_actions_for_user(user_pk: str | int, limit: int) -> QuerySet[LogEntry]:
+    """Return the most recent ``LogEntry`` rows for one user, newest first.
+
+    The user-scoped counterpart of :func:`object_log_entries`: filtered by
+    the acting user and capped at ``limit`` — exactly how Django's admin
+    index "Recent actions" panel reads the log
+    (``LogEntry.objects.filter(user=...)``). Same get_queryset-rule
+    rationale as the module docstring: LogEntry is a framework audit
+    table, not a consumer model, so it is read directly here (outside
+    ``api/``) rather than via ``ModelAdmin.get_queryset``.
+    """
+    return LogEntry.objects.filter(user__pk=user_pk).order_by("-action_time")[:limit]

{django_admin_react-0.2.0a7 → django_admin_react-1.0.0}/django_admin_react/conf.py

@@ -22,6 +22,12 @@ from django.conf import settings as django_settings
 
 DEFAULTS: dict[str, Any] = {
     "ADMIN_SITE": "django.contrib.admin.site",
+    # The list page size derives from the model's
+    # ``ModelAdmin.list_per_page`` (Django's changelist source of truth,
+    # Rule #1 / #281), so the SPA pages like the HTML admin with no extra
+    # setting. ``DEFAULT_PAGE_SIZE`` is the fallback only when
+    # ``list_per_page`` is missing / invalid. ``MAX_PAGE_SIZE`` always caps
+    # ``?page_size`` (a DoS guard).
     "DEFAULT_PAGE_SIZE": 25,
     "MAX_PAGE_SIZE": 200,
     "ENABLE_PROFILING": False,
@@ -29,16 +35,23 @@ DEFAULTS: dict[str, Any] = {
     # rendered server-side into the SPA index template so the SPA
     # picks them up on first paint (no FOUC).
     #
-    # ``BRAND_TITLE``      — string shown in the sidebar header *and*
-    #                        the browser tab title. ``None`` (default)
-    #                        falls back to the configured AdminSite's
-    #                        ``site_header`` if set, else the package
-    #                        name. Plain text; no HTML.
-    # ``BRAND_LOGO_URL``   — URL to a square logo / favicon. Written
-    #                        into the SPA's ``<link rel="icon">``.
-    #                        ``None`` (default) keeps the no-op
-    #                        ``data:,`` placeholder. Either an absolute
-    #                        URL or a path under your ``STATIC_URL``.
+    # ``BRAND_TITLE``      — optional override for *both* the sidebar
+    #                        header and the browser-tab title. ``None``
+    #                        (default) derives them from the AdminSite,
+    #                        mirroring Django admin: ``site_header`` →
+    #                        sidebar header, ``site_title`` → tab title
+    #                        (falling back to ``site_header``), else the
+    #                        package name (#281). A consumer who already
+    #                        set ``site_header`` / ``site_title`` on their
+    #                        ``AdminSite`` needs no branding setting at all.
+    #                        Plain text; no HTML.
+    # ``BRAND_LOGO_URL``   — optional override for the logo / favicon URL,
+    #                        written into the SPA's ``<link rel="icon">``.
+    #                        ``None`` (default) reads ``site_logo`` off the
+    #                        configured ``AdminSite`` if the consumer set
+    #                        that attribute (#281), else keeps the no-op
+    #                        ``data:,`` placeholder. Either an absolute URL
+    #                        or a path under your ``STATIC_URL``.
     "BRAND_TITLE": None,
     "BRAND_LOGO_URL": None,
     # ``PRIMARY_COLOR`` — the accent color for primary buttons, links, and
@@ -49,19 +62,20 @@ DEFAULTS: dict[str, Any] = {
     # falls back to this default, since the value is written into a
     # ``<style>`` block and must not be able to inject CSS.
     "PRIMARY_COLOR": "#2563eb",
-    # ``REACT_LOGIN`` — opt-in React-rendered login (Issue #167).
-    # Default ``False`` keeps today's behavior: ``SpaIndexView``
-    # redirects anonymous / unauthorized users to Django's HTML login
-    # (or the package's own ``<mount>/login/`` page). When ``True``,
-    # the SPA shell is served to anonymous users (with the CSRF cookie
-    # set) so the React app can render its own login form, which POSTs
-    # to ``/api/v1/login/``. The auth *mechanism* is unchanged — still
-    # Django's ``authenticate``/``login`` behind the JSON endpoint
-    # (`api/views/auth.py`); only the UI surface differs. The shell
-    # carries no user data, so serving it to anonymous users discloses
-    # nothing the static bundle wouldn't, and every data API call still
-    # returns 403 until the user authenticates.
-    "REACT_LOGIN": False,
+    # ``REACT_LOGIN`` — React-rendered login is the **default** so the
+    # SPA fully replaces the Django admin URL surface end-to-end (owner
+    # directive 2026-05-28). ``SpaIndexView`` serves the React shell to
+    # anonymous users (with the CSRF cookie set) and the in-SPA login
+    # form POSTs to the API package's ``/api/v1/login/``. A consumer
+    # who wants the legacy HTML-admin login back can opt out with
+    # ``"REACT_LOGIN": False`` — the package's own ``<mount>/login/``
+    # endpoint is still mounted in either mode. The auth *mechanism* is
+    # unchanged in both modes (Django's ``authenticate``/``login``
+    # behind the JSON endpoint); only the UI surface differs. The
+    # shell carries no user data — serving it to anonymous users
+    # discloses nothing the static bundle wouldn't, and every data API
+    # call still returns 403 until the user authenticates.
+    "REACT_LOGIN": True,
     # PWA (Issue #86) — all optional; sane defaults make the manifest
     # work with zero config. See ``django_admin_react/pwa.py`` +
     # ``docs/ux/pwa.md``.
@@ -74,6 +88,17 @@ DEFAULTS: dict[str, Any] = {
     #                      dicts. ``None`` (default) uses the shipped
     #                      192/512/maskable set under
     #                      ``static/dar/icons/``.
+    # ``API_URL_PREFIX`` — absolute URL prefix the SPA calls for every
+    # JSON request (#559). Default ``None`` keeps the inline include the
+    # package ships today (`<spa-mount>/api/v1/`), so existing consumers
+    # are unaffected. Override when the consumer mounts
+    # ``django_admin_rest_api.urls`` separately and the SPA should talk
+    # to **that** mount instead — for example
+    # ``DJANGO_ADMIN_REACT = {"API_URL_PREFIX": "/api/api/v1/"}`` lets
+    # the SPA and any other client share a single REST mount. When set,
+    # `django_admin_react.urls` skips the inline `api/v1/` include so
+    # there is no double-mount.
+    "API_URL_PREFIX": None,
     "PWA_NAME": None,
     "PWA_SHORT_NAME": None,
     "PWA_ICONS": None,
@@ -96,6 +121,7 @@ class _PackageSettings:
     BRAND_LOGO_URL: str | None = DEFAULTS["BRAND_LOGO_URL"]
     PRIMARY_COLOR: str = DEFAULTS["PRIMARY_COLOR"]
     REACT_LOGIN: bool = DEFAULTS["REACT_LOGIN"]
+    API_URL_PREFIX: str | None = DEFAULTS["API_URL_PREFIX"]
     PWA_NAME: str | None = DEFAULTS["PWA_NAME"]
     PWA_SHORT_NAME: str | None = DEFAULTS["PWA_SHORT_NAME"]
     PWA_ICONS: list[dict[str, str]] | None = DEFAULTS["PWA_ICONS"]

{django_admin_react-0.2.0a7 → django_admin_react-1.0.0}/django_admin_react/pwa.py

@@ -34,7 +34,11 @@ from django.shortcuts import render
 from django.views.generic import View
 
 from django_admin_react import conf as dar_conf
-from django_admin_react.api.registry import get_admin_site
+
+# Re-use the API package's admin-site lookup (this repo implements no
+# API; the registry helper lives there). The PWA only needs the active
+# `AdminSite.name` for the manifest's start URL.
+from django_admin_rest_api.api.registry import get_admin_site
 
 # Theme colours keyed by the resolved colour scheme. Kept here (not in
 # the SPA's CSS-var system) because the manifest is rendered server-side

{django_admin_react-0.2.0a7 → django_admin_react-1.0.0}/django_admin_react/static/admin_react/.vite/manifest.json

@@ -1,11 +1,11 @@
 {
   "index.html": {
-    "file": "assets/index-BK8mlqvA.js",
+    "file": "assets/index-CcvXnwTT.js",
     "name": "index",
     "src": "index.html",
     "isEntry": true,
     "css": [
-      "assets/index-BVqO3W_r.css"
+      "assets/index-Rr7dwEhe.css"
     ]
   }
 }