Closed aliTanveerAnalog closed 1 year ago
So did a git bisect
and found 3b7b503
to be the first commit causing a crash, but the example stops working and starts giving js errors with commit 047ed1e
. @Demonthos any ideas?
The value
attribute is volatile (must be set every render even if it has not changed), but if it is static it does not have an id on the renderer because it never needs to be updated.
A temporary fix to this is setting value to r#"{""}"#
which marks it as dynamic and assigns it a id.
This means we don't know which parts of the node will be traversed to when creating the macro. We cannot generate the traversal path (the way we assign ids on master) or using child node paths from a root (what #600 uses) without knowing if the attribute is volatile or not.
This is partially fixed
It no longer panics but there is still a difference between using r#"{""}"#
and ""
:
r#"{""}"#
marks applies the volatile property (which causes the text area to clear after clicking the button), but ""
does not apply the volatile property (so the text area is not cleared)
Problem
Option::unwrap()
on aNone
value'" while setting a global/local or ref state in component.Steps To Reproduce
Expected behavior
Screenshots
Environment:
master
]nightly
]web
,desktop
]BACKTRACE LOGS
Questionnaire