Mark Gibbs comments

Results 51 comments of


                                            Mark Gibbs

Support for `@app.long_callback` and improved documentation of asynchronous stack

@zachsiegel-capsida if it (ie some processing) is something long running, then solving it in a mainstream django way (eg celery) might be worth considering, although obviously it depends a lot...

Support for `@app.long_callback` and improved documentation of asynchronous stack

@zachsiegel-capsida you (should) get the error message, as at the moment the package requirement is for Django < 4.0 - this is essentially as it hasn't been validated yet. In...

Support for `@app.long_callback` and improved documentation of asynchronous stack

Note that #403 is the task to move to Django 4.0

Allow JSON encoder to be set

See PR #408

The package generates Django migrations in the path of the pip package and not in the application migrations folder

@erl987 What version are you running? If I take the current release (git checkout of the master branch), create the environment, cd to the demo directory and then execute ./manage.py...

bootstrap 5 compatibility

I suspect that at the moment you'll get a mix of bootstrap 4 and 5 being used. If you are in a position to try it and report what you...

Using lazy_gettext with components breaks JSON encoding

@danjac the immediate issue should be fixable with a different JSON encoder; this work has been captured in #405

stuck at "loading" for demo 3,4,6,7,9 and also when rendering dash_pivottable compoment

@luyi1678 what happens if you use a version of Dash < 1.21 as well as the 2.4.0 version of channels? As per #349 there are outstanding issues with version 1.21...

TypeError: i[v][g] is undefined

@zepp133 you will have to share a bit more information about what you have (and have not) done. As a first step, what exactly does 'without any changes' mean? Have...

Live-Updating: `ValueError: No route found for path 'dpd/ws/channel'`

There is now a new version of routing.py in v2.2.0 as part of the move to supporting Django 4.0 However, for sure the approach that is essentially imposed by channels...