reactpy
reactpy copied to clipboard
reactive-python
It's React, but in Python
### Current Situation Currently, if an invalid hook call occurs then ReactPy completely breaks. Reference - #646 - #610 ### Proposed Actions Add an error boundary to tree nodes to...
### Current Situation We currently use standard JavaScript websockets for client/server communication. The downside of this is that they have no method of handling backpressure, which will become a realistic...
### Current Situation Currently, creating a custom component requires manual steps. Namely, the developer must use the [template repository](https://github.com/reactive-python/reactpy-js-component-template) and `pip install cookiecutter`. Since the template repo is a Git...
### Current Situation Currently, data attributes are not serialized, such as in the context of events. ### Proposed Actions Serialize Data attributes and pass this information into the Python portions...
### Current Situation Currently we don't document that using the unpacking operator (`*args`) has undesirable consequences on whether we do or don't warn about missing keys. ### Proposed Actions Document...
Using the unpack operator is dangerous within a component's `return`. ReactPy relies on the position of child elements to keep track of hooks (for any element that doesn't have a...
### Current Situation Presently, if connection to a websocket is lost we log to the console. This is fine for debugging purposes, but for users it could be frustrating if...
Right now we don't serialize file content. Just metadata. Along with this we'll want to allow users to configure the max message size to help users protect against large file...
# Current Situation Currently, IDOM can render [roughly 18 simple components per second](https://github.com/idom-team/django-idom/pull/23#issuecomment-999975499). # Proposed Changes Find the hot spots in IDOM's code-base in order to identify where attention should...
### Current Situation There currently is no convenient way of reacting to WS disconnection within components without doing so in the JavaScript `websocket.onclose` event. ### Proposed Changes Allow all components...