You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm not sure if this is related to #243, as I've been forced to use the interpolation method for updating values (e.g., text="value: {{username}};"), due to bind-item not working as expected.
The issue is that I can't seem to get the bound entity components to update if the key does not change in the object.
As am example, I'd like to be able to update username in the following object, while using clientId as the key, since it is unique.
I've come up with a hacky workaround by using a separate id which is assigned a value with Date.now() appended, but then I need to remove and replace the user in order to get any updates, which also disturbs the display order.
To clarify, I can update the value in state, but changes are not reflected in the bound components.
I've tried using state.users.__dirty = true; to no avail.
Any guidance would be awesome.
Thanks for all you do.
The text was updated successfully, but these errors were encountered:
I'm not sure if this is related to #243, as I've been forced to use the interpolation method for updating values (e.g.,
text="value: {{username}};"
), due tobind-item
not working as expected.The issue is that I can't seem to get the bound entity components to update if the
key
does not change in the object.As am example, I'd like to be able to update
username
in the following object, while usingclientId
as thekey
, since it is unique.I've come up with a hacky workaround by using a separate id which is assigned a value with
Date.now()
appended, but then I need to remove and replace the user in order to get any updates, which also disturbs the display order.To clarify, I can update the value in state, but changes are not reflected in the bound components.
I've tried using
state.users.__dirty = true;
to no avail.Any guidance would be awesome.
Thanks for all you do.
The text was updated successfully, but these errors were encountered: