reflex-django 0.1.0__tar.gz

reflex_django-0.1.0/.gitignore

@@ -0,0 +1,14 @@
+__pycache__/
+*.py[cod]
+*$py.class
+*.egg-info/
+.eggs/
+dist/
+build/
+.venv/
+.venv*/
+.pytest_cache/
+.coverage
+htmlcov/
+.mypy_cache/
+.ruff_cache/

reflex_django-0.1.0/CHANGELOG.md

@@ -0,0 +1,27 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+### Changed (breaking)
+
+- `DjangoUserState` snapshot field names no longer use a `django_` prefix:
+  `django_user_id` → `user_id`, `django_username` → `username`,
+  `django_email` → `email`, `django_first_name` → `first_name`,
+  `django_last_name` → `last_name`, `django_is_authenticated` → `is_authenticated`,
+  `django_is_staff` → `is_staff`, `django_is_superuser` → `is_superuser`,
+  `django_group_names` → `group_names`.
+
+## [0.1.0] — 2026-05-14
+
+### Added
+
+- Initial PyPI-ready release of `reflex-django`: Django ASGI integration with
+  Reflex (`ReflexDjangoPlugin`), `DjangoEventBridge`, auth/session/locale
+  bridging, context processors, helpers, and CLI entry point `reflex-django`.
+
+[0.1.0]: https://pypi.org/project/reflex-django/

reflex_django-0.1.0/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        https://www.apache.org/licenses/LICENSE-2.0
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2023, Pynecone, Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

reflex_django-0.1.0/PKG-INFO

@@ -0,0 +1,346 @@
+Metadata-Version: 2.4
+Name: reflex-django
+Version: 0.1.0
+Summary: Run a Django backend (Django ORM, Django Admin) alongside a Reflex app.
+Project-URL: homepage, https://reflex.dev
+Project-URL: documentation, https://github.com/reflex-dev/reflex/tree/main/packages/reflex-django
+Project-URL: repository, https://github.com/reflex-dev/reflex
+Project-URL: changelog, https://github.com/reflex-dev/reflex/releases
+Author: Reflex Contributors
+Maintainer: Reflex Contributors
+Maintainer-email: maintainers@reflex.dev
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: admin,asgi,django,fullstack,orm,reflex
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Web Environment
+Classifier: Framework :: Django
+Classifier: Framework :: Django :: 6.0
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Internet :: WWW/HTTP :: Dynamic Content
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Typing :: Typed
+Requires-Python: <4.0,>=3.12
+Requires-Dist: asgiref>=3.8
+Requires-Dist: click>=8.0
+Requires-Dist: django<7.0,>=6.0
+Requires-Dist: reflex<1.0,>=0.9.2
+Description-Content-Type: text/markdown
+
+# reflex-django
+
+## Table of contents
+
+1. [About reflex-django](#about-reflex-django)
+2. [Architecture](#architecture)
+3. [How to set up](#how-to-set-up)
+4. [Commands](#commands)
+5. [States, context, and bridges](#states-context-and-bridges)
+
+---
+
+## About reflex-django
+
+**reflex-django** is a [Reflex](https://reflex.dev) plugin that runs a **Django ASGI** application and your **Reflex** app in **one process** under a single dev command (`reflex run`). HTTP requests whose paths match configured prefixes (for example Django Admin, optional API routes, and path-based static URLs) are forwarded to Django. Everything else—including the compiled Reflex frontend and Reflex’s Socket.IO event channel under `/_event/…`—is handled by Reflex.
+
+**Why it exists.** Reflex gives you a Python-first reactive UI. Django gives you the ORM, migrations, the admin, sessions, authentication, internationalization, and the ecosystem of HTTP views and middleware you already rely on. reflex-django lets you keep that Django surface area without standing up a separate HTTP server for local development or simple deployments, while still using Reflex for the interactive UI.
+
+**Why Django developers need it.** Reflex user actions arrive over WebSocket events, not through Django’s normal request/response cycle, so Django’s HTTP middleware (sessions, auth, locale) does not run for those events by default. reflex-django adds an explicit **event bridge** that rebuilds a synthetic `HttpRequest` from the browser data Reflex provides, attaches the session and user, and exposes that request through small APIs your event handlers can call. A separate **HTTP bridge** routes ordinary browser HTTP traffic on selected path prefixes to Django’s ASGI app. Together, these bridges make Django session auth and related patterns usable from Reflex without pretending the two stacks share one router.
+
+**Author.** This package is written by **Mohannad Irshedat**.
+
+| Topic   | Versions |
+|---------|----------|
+| Django  | 6.0.x    |
+| Python  | 3.12+    |
+
+---
+
+## Architecture
+
+At a high level, reflex-django does three coordinated things:
+
+1. **Plugin bootstrap** — When `rxconfig.py` is loaded, `ReflexDjangoPlugin` sets `DJANGO_SETTINGS_MODULE` (if you pass `settings_module`), exports path prefix environment variables used by Django settings, and calls `configure_django()` so Django is initialized before your Reflex app module imports models or translation helpers.
+
+2. **HTTP ASGI composition** — After Reflex compiles your app, the plugin appends an `api_transformer` that wraps Reflex’s inner ASGI app. Incoming HTTP (and WebSocket upgrade traffic where applicable) is dispatched by **URL path prefix**: matching prefixes go to Django’s ASGI application (optionally wrapped for static files); non-matching traffic stays on Reflex. ASGI lifespan events are owned by Reflex.
+
+3. **Per-event Django context** — When `install_event_bridge` is true (the default), Reflex registers `DjangoEventBridge` middleware. On each Reflex event, the bridge builds a synthetic `django.http.HttpRequest` from `event.router_data` (cookies, headers, client IP, path), loads the Django session, optionally applies the same locale negotiation as `LocaleMiddleware`, resolves `request.user` via Django’s async `aget_user`, and binds that request on a **context variable** for the duration of the event. Your handlers call `current_user()`, `current_request()`, and related helpers, which read that binding.
+
+.
+
+![img.png](img.png)
+
+
+
+---
+
+## How to set up
+
+Use **uv** to create a project, add dependencies, scaffold the Reflex frontend, create a Django project, then wire the plugin in `rxconfig.py`.
+
+1. Initialize a Python project:
+
+   ```bash
+   uv init
+   ```
+
+2. Add Reflex and reflex-django:
+
+   ```bash
+   uv add reflex reflex-django
+   ```
+
+3. Initialize the Reflex frontend (app name and layout follow Reflex’s CLI):
+
+   ```bash
+   uv run reflex init frontend
+   ```
+
+4. Create a Django project package named `backend` (adjust the name if you prefer):
+
+   ```bash
+   uv run django-admin startproject backend .
+   ```
+
+   This typically produces `backend/settings.py`, `backend/urls.py`, and `manage.py` in the current directory.
+
+5. Configure **`rxconfig.py`** so Reflex loads Django with your settings module. Import the plugin and pass `settings_module` as the dotted path to your Django settings (for example `backend.settings`):
+
+   ```python
+   import reflex as rx
+   from reflex_django import ReflexDjangoPlugin
+
+   config = rx.Config(
+       app_name="myapp",
+       plugins=[
+           ReflexDjangoPlugin(settings_module="backend.settings"),
+       ],
+   )
+   ```
+
+**Minimal Django expectations.** Your `INSTALLED_APPS` should include the Django contrib apps you need (for example `django.contrib.auth`, `django.contrib.sessions`, and often `django.contrib.admin`) and **`reflex_django`** if you use bundled helpers. Set `ROOT_URLCONF` and mount admin (and any HTTP routes under an optional `backend_prefix`) so path-based routing matches what you configure on `ReflexDjangoPlugin`. Run the app with:
+
+```bash
+uv run reflex run
+```
+
+---
+
+## Commands
+
+reflex-django registers a **`django`** command group on the **`reflex`** CLI (via a small import hook installed with the package) and also ships a standalone console script **`reflex-django`**.
+
+**Running Django management commands**
+
+- Through Reflex:
+
+  ```bash
+  uv run reflex django migrate
+  uv run reflex django makemigrations
+  uv run reflex django createsuperuser
+  uv run reflex django shell
+  uv run reflex django collectstatic
+  uv run reflex django help
+  ```
+
+- Through the standalone entry point (equivalent forwarding for normal manage.py subcommands):
+
+  ```bash
+  uv run reflex-django migrate
+  uv run reflex-django help
+  ```
+
+Any subcommand name other than the special cases below is forwarded to Django’s `execute_from_command_line`. The wrapper first loads your **`rxconfig`** (so `ReflexDjangoPlugin` can set `DJANGO_SETTINGS_MODULE` and path prefixes) and then calls **`configure_django()`**, so the same settings module Reflex uses at runtime is used for migrations and other management commands.
+
+**Init scaffolding (omitted here).** `reflex django init` and `reflex-django init` exist to scaffold a starter tree but are considered **beta**; this README does not document them. Prefer the manual flow in [How to set up](#how-to-set-up) above.
+
+---
+
+## States, context, and bridges
+
+This section walks through Reflex state, Django’s per-event request context (context variables), the two bridges, and the helper states that mirror Django into Reflex UI state—each with a small example.
+
+### Reflex `rx.State` (baseline)
+
+In Reflex, a **State** class subclasses `rx.State`. Fields you declare are synchronized with the client where appropriate; values must be **JSON-serializable** when they cross the wire. You define event handlers with `@rx.event` (often `async def` when you call async Django APIs).
+
+```python
+import reflex as rx
+
+
+class CounterState(rx.State):
+    count: int = 0
+
+    @rx.event
+    def increment(self):
+        self.count += 1
+```
+
+### Per-event Django context (`reflex_django.context`)
+
+Reflex events do not carry a Django `HttpRequest` object. reflex-django stores the synthetic request built for the current event on a **context variable**. Public read helpers:
+
+| Function | Role |
+|----------|------|
+| `current_request()` | Bound `HttpRequest` or `None` outside an event without the bridge |
+| `current_user()` | Django user or `AnonymousUser` |
+| `current_session()` | Session backend instance or `None` |
+| `current_language()` | Active language code after locale activation |
+
+Lower-level **`begin_event_request(request)`** and **`end_event_request()`** are used by the bridge and for tests or advanced scenarios; application code normally relies on the helpers above inside `@rx.event` handlers.
+
+```python
+import reflex as rx
+from reflex_django import current_user
+
+
+class WhoamiState(rx.State):
+    label: str = ""
+
+    @rx.event
+    async def refresh(self):
+        user = current_user()
+        self.label = user.get_username() if user.is_authenticated else "anonymous"
+```
+
+### Bridge 1 — HTTP ASGI path dispatcher
+
+`ReflexDjangoPlugin` installs an **`api_transformer`** that wraps Reflex’s ASGI app. Requests whose path starts with any configured prefix are sent to Django’s ASGI app; other paths stay on Reflex. Relevant plugin arguments:
+
+| Argument | Meaning |
+|----------|---------|
+| `backend_prefix` | Optional prefix for your own Django HTTP routes (for example `"/api"`) |
+| `admin_prefix` | Prefix for Django Admin (default `"/admin"`) |
+| `extra_prefixes` | Additional path prefixes routed to Django |
+| `install_event_bridge` | When `True`, registers `DjangoEventBridge` (default) |
+
+```python
+ReflexDjangoPlugin(
+    settings_module="backend.settings",
+    backend_prefix="/api",
+    admin_prefix="/admin",
+    extra_prefixes=("/billing",),
+)
+```
+
+Your `ROOT_URLCONF` must define routes under those prefixes so Django can serve them.
+
+### Bridge 2 — `DjangoEventBridge` (Reflex middleware)
+
+**`DjangoEventBridge`** runs at the start of each Reflex event. It constructs a synthetic `HttpRequest`, attaches the session, optionally runs locale negotiation when `USE_I18N` and `REFLEX_DJANGO_I18N_EVENT_BRIDGE` allow it, and sets `request.user` using **`aget_user`**. It then calls `begin_event_request(request)` so `current_user()` and friends work in your handlers.
+
+To disable this behavior (for example if you do not use Django session auth from Reflex):
+
+```python
+ReflexDjangoPlugin(settings_module="backend.settings", install_event_bridge=False)
+```
+
+### `DjangoUserState`
+
+**`DjangoUserState`** is a `rx.State` subclass that mirrors a JSON-safe snapshot of the current user (`user_id`, `username`, `email`, names, `is_authenticated`, staff/superuser flags, optional `group_names`). Use it for navbar and conditional UI.
+
+- Call **`sync_from_django`** from a page’s **`on_load`** (it is an `@rx.event`).
+- After login or logout, call **`await self.refresh_django_user_fields()`** from an async handler so the snapshot updates without a full navigation when appropriate.
+
+Server-side authorization must still use **`current_user()`** (or stricter checks); client-visible state is for display only.
+
+```python
+import reflex as rx
+from reflex_django import DjangoUserState
+
+
+class AuthState(DjangoUserState):
+    pass
+
+
+app = rx.App()
+
+# app.add_page(index, on_load=AuthState.sync_from_django)
+```
+
+### `DjangoI18nState`
+
+**`DjangoI18nState`** exposes **`django_language_code`** and **`django_language_bidi`**, aligned with Django’s active language after the event bridge. Use **`sync_from_django`** on `on_load`, or **`await self.refresh_django_i18n_fields()`** after the user changes language via a Django-served view.
+
+```python
+import reflex as rx
+from reflex_django import DjangoI18nState
+
+
+app = rx.App()
+
+# app.add_page(home, on_load=DjangoI18nState.sync_from_django)
+```
+
+### Reflex-facing Django context (processors and `DjangoContextState`)
+
+Reflex serializes state to the browser, so any dict you merge into Reflex state must be **JSON-serializable**.
+
+**Two configuration modes** (see `reflex_django.reflex_context`):
+
+1. **`REFLEX_DJANGO_CONTEXT_PROCESSORS`** — A non-empty tuple of dotted paths to callables `(request) -> dict` (or async). When this list is set, it is used exclusively. You are responsible for JSON-safe values.
+
+2. **Template context processors** — If `REFLEX_DJANGO_CONTEXT_PROCESSORS` is empty and **`REFLEX_DJANGO_USE_TEMPLATE_CONTEXT_PROCESSORS`** is `True`, the same dotted paths as in `TEMPLATES[*].OPTIONS["context_processors"]` are run, with built-in sanitization (for example `user` becomes a snapshot; `request`, `perms`, `messages` are omitted; other values must pass plain `json.dumps`).
+
+Built-in processor callables you can list explicitly:
+
+- **`reflex_django.reflex_context.builtin_user_context`** — adds a template-shaped `user` key as a snapshot dict.
+- **`reflex_django.reflex_context.builtin_i18n_context`** — adds `LANGUAGE_CODE`, `LANGUAGE_BIDI`, and `LANGUAGES`.
+
+Example settings snippet:
+
+```python
+REFLEX_DJANGO_CONTEXT_PROCESSORS = (
+    "reflex_django.reflex_context.builtin_user_context",
+    "reflex_django.reflex_context.builtin_i18n_context",
+)
+```
+
+**`collect_reflex_context(request)`** runs the configured processor list and returns one merged dict. You can await it inside a handler when `current_request()` is bound:
+
+```python
+from reflex_django import current_request
+from reflex_django.reflex_context import collect_reflex_context
+
+
+@rx.event
+async def debug_context(self):
+    merged = await collect_reflex_context(current_request())
+    # use merged (e.g. assign JSON-safe keys to state)
+```
+
+**`DjangoContextState`** holds **`django_context`** and a stringified **`django_context_json`**. Call **`load_django_context`** from `on_load` to populate them from processors using the bound request:
+
+```python
+from reflex_django import DjangoContextState
+
+
+# app.add_page(about, on_load=DjangoContextState.load_django_context)
+```
+
+Helper functions **`template_context_processor_paths()`** and **`reflex_context_processor_paths()`** introspect settings for tooling or documentation.
+
+### `user_snapshot` vs `current_user`
+
+**`user_snapshot(user)`** returns the same flat dict shape used by `DjangoUserState`, given a user instance. It is useful in custom context processors, tests, or logging—without touching Reflex state.
+
+**`current_user()`** returns the live Django user (or anonymous) for the **current Reflex event** after the bridge runs. Use it for **permissions, ownership checks, and mutations** on the server.
+
+**`DjangoUserState`** fields are a **UI snapshot**; always re-check authorization with `current_user()` (or equivalent) inside event handlers that change data.
+
+```python
+from reflex_django import current_user
+from reflex_django.auth_state import user_snapshot
+
+
+@rx.event
+async def audit_banner(self):
+    self.snapshot_json = user_snapshot(current_user())  # dict for display
+    assert current_user().is_authenticated  # real check for protected actions
+```