Releases: reactive-python/reactpy
0.36.3
0.36.2
0.36.1
Includes bug fixes and renames the configuration option IDOM_WED_MODULES_DIR
to IDOM_WEB_MODULES_DIR
with a corresponding deprecation warning.
Closed Issues
Merged Pull Requests
0.36.0
This release includes an important fix for errors produced after #623 was merged. In addition there is not a new http.script
element which can behave similarly to a standard HTML <script>
or, if no attributes are given, operate similarly to an effect. If no attributes are given, and when the script evaluates to a function, that function will be called the first time it is mounted and any time the content of the script is subsequently changed. If the function then returns another function, that returned function will be called when the script is removed from the view, or just before the content of the script changes.
Closed Issues
Pull Requests
0.35.4
0.35.3
0.35.2
This release includes several bug fixes. The most significant of which is the ability to change the type of an element in the try (i.e. to and from being a component) without getting an error. Originally the errors were introduced because it was though changing element type would not be desirable. This was not the case though - swapping types turns out to be quite common and useful.
0.35.1
0.35.0
The highlight of this release is that the default "key" of all elements will be their index amongst their neighbors. Previously this behavior could be engaged by setting IDOM_FEATURE_INDEX_AS_DEFAULT_KEY=1
when running IDOM. In this release though, you will need to explicitely turn off this feature (i.e. =0
) to return to the old behavior. With this change, some may notice additional error logs which warn that:
Key not specified for child in list ...
This is saying is that an element or component which was created in a list does not have a unique key
. For more information on how to mitigate this warning refer to the docs on "Organizing Items With Keys".
Closed Issues
Pull Requests
0.34.0
This release contains a variety of minor fixes and improvements which came out of rewriting the documentation. The most significant of these changes is the remove of target element attributes from the top-level of event data dictionaries. For example,
instead of being able to find the value of an input at event["value"]
it willinstead be found at event["target"]["value"]
. For a short period we will issue a DeprecationWarning
when target attributes are requested at the top-level of the event dictionary. As part of this change we also add event["currentTarget"]
and event["relatedTarget"]
keys to the event dictionary as well as a
event[some_target]["boundingClientRect"]
where some_target
may be "target"
, "currentTarget"
or "relatedTarget"
.
Closed Issues
- Move target attributes to
event['target']
- #548
Pull Requests