Releases: reactive-python/reactpy-django
Releases · reactive-python/reactpy-django
3.3.0
Added
- Added system checks for a variety of common ReactPy misconfigurations.
REACTPY_BACKHAUL_THREAD
setting to enable/disable threading behavior.
Changed
- If using
settings.py:REACTPY_DATABASE
,reactpy_django.database.Router
must now be registered insettings.py:DATABASE_ROUTERS
. - By default, ReactPy will now use a backhaul thread to increase performance.
- Minimum Python version required is now
3.9
- A thread-safe cache is no longer required.
3.2.1
Added
- Template tag exception details are now rendered on the webpage when
settings.py:DEBUG
is enabled.
Fixed
- Prevent exceptions within the
component
template tag from causing the whole template to fail to render.
3.2.0
Added
- Added warning if poor system/cache/database performance is detected while in
DEBUG
mode. - Added
REACTPY_AUTH_BACKEND
setting to allow for custom authentication backends.
Changed
- Using
SessionMiddlewareStack
is now optional. - Using
AuthMiddlewareStack
is now optional.
3.1.0
Added
use_query
now supports async functions.use_mutation
now supports async functions.reactpy_django.types.QueryOptions.thread_sensitive
option to customize how sync queries are executed.reactpy_django.hooks.use_mutation
now acceptsreactpy_django.types.MutationOptions
option to customize how mutations are executed.
Changed
- The
mutate
argument onreactpy_django.hooks.use_mutation
has been renamed tomutation
.
Fixed
- Fix bug where ReactPy utilizes Django's default cache timeout, which can prematurely expire the component cache.
3.0.1
Removed
django-reactpy
database entries are no longer cleaned during Django application startup. Instead, it will occur on webpage loads ifREACTPY_RECONNECT_MAX
seconds has elapsed since the last cleaning.
3.0.1-legacy-idom
Changed
- Add warning to
django-idom
for users to usereactpy-django
instead.
3.0.0-reactpy
Changed
django-idom
has been renamed toreactpy-django
! Please note that all references to the wordidom
in your code should be changed toreactpy
. See the docs for more details.
3.0.0
This is Django-IDOM's biggest update yet!
To upgrade from previous version you will need to...
- Install
django-idom >= 3.0.0
- Run
idom rewrite-keys <DIR>
andidom rewrite-camel-case-props <DIR>
to update youridom.html.*
calls to the new syntax - Run
python manage.py migrate
to create the new Django-IDOM database entries
Added
- The
idom
client will automatically configure itself to debug mode depending onsettings.py:DEBUG
. use_connection
hook for returning the browser's activeConnection
.IDOM_CACHE
is now configurable withinsettings.py
to whatever cache name you wish.
Changed
- It is now mandatory to run
manage.py migrate
after installing IDOM. - Bumped the minimum IDOM version to 1.0.0. Due to IDOM 1.0.0,
idom.html.*
...- HTML properties can now be
snake_case
. For exampleclassName
now becomesclass_name
. key=...
is now declared within the propsdict
(rather than as akwarg
).
- HTML properties can now be
- The
component
template tag now supports both positional and keyword arguments. - The
component
template tag now supports non-serializable arguments. IDOM_WS_MAX_RECONNECT_TIMEOUT
setting has been renamed toIDOM_RECONNECT_MAX
.
Removed
django_idom.hooks.use_websocket
has been removed. The similar replacement isdjango_idom.hooks.use_connection
.django_idom.types.IdomWebsocket
has been removed. The similar replacement isdjango_idom.types.Connection
.settings.py:CACHE['idom']
is no longer used by default. The name of the cache back-end must now be specified with theIDOM_CACHE
setting.
Fixed
view_to_component
will now retain the contents of a<head>
tag when rendering.- React client is now set to
production
rather thandevelopment
. use_query
will now utilizefield.related_name
when postprocessing many-to-one relationships.
Security
- Fixed a potential method of component template tag argument spoofing.
- Exception information will no longer be displayed on the page, based on the value of
settings.py:DEBUG
.
3.0.0a4
- Bump IDOM to
1.0.0a6
3.0.0a3
- Bump idom to
1.0.0a5
- Prevent
db_cleanup
from causing startup failure on anyDatabaseError
, rather than justOperationalError(DatabaseError)
IDOM_DATABASE
settingIDOM_CACHE
setting