Mark Bakhit
Mark Bakhit
### Current Situation Sometimes `django_form` events such as `on_error` will not be executed. This appears to be caused by a race condition where the `use_effect(render_form)` hook could be cancelled prior...
### Current Situation ReactPy currently uses websockets as the primary messaging method for rendering. This can be problematic because cloud providers (such as `Azure` or `GCP`) do not keep web...
### Current Situation and Proposed Actions There are currently a few resolvable limitations of `view_to_iframe`. - [ ] No built-in method of signalling events back to the parent component. -...
### Current Situation and Proposed Actions --- The following fields are currently incompatible with `django_form` due to ReactPy's [client](https://github.com/reactive-python/reactpy-django/tree/c8b4ec08ab7c701a443e8fff8e734a5e76700857/src/js/src) and [server](https://github.com/reactive-python/reactpy-django/blob/c8b4ec08ab7c701a443e8fff8e734a5e76700857/src/reactpy_django/websocket/consumer.py) not supporting file serialization: - [ ] `FileField` -...
### Current Situation and Proposed Actions There are currently several limitations of using `view_to_component`. - [ ] Requires manual intervention to change HTTP methods to anything other than `GET`. -...
### Current Situation We currently don't run code coverage on `reactpy-django` ### Proposed Actions Add coverage tests to this repository. Thankfully this is pretty simple to do using `hatch`, as...
### Description We currently use a handful of testing functions for sending/receiving data to our ASGI/WSGI apps. Would be easier to [use HTTPX](https://www.python-httpx.org/advanced/transports/#asgi-transport) to do the same task.
### Description Right now we only hit ~96% coverage when running `hatch test --cover --all`. A few more tests will need to be added to reach 100% coverage.
### Description Currently unit tests are run using dummy servers (based on legacy whitenoise tests), but I personally am not a fan of dummy tests. Long term it would be...
### Description The `_nostatic` denotator in `runserver_nostatic` is a bit confusing without background knowledge. There are several options available for better names - `servestatic.override_runserver` - `servestatic.override_runserver_cmd` - `servestatic.override_runserver_with_servestatic` - `servestatic.runserver`...