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
We currently have an issue where performUpdate is doing double duty. Users can override it to schedule updates, but we also recommend that users can call it to make an update synchronous. To resolve this, we'll add scheduleUpdate and recommend users override that for scheduling and use performUpdate to make the update "go" synchronously.
We also need to update the docs on lit.dev to reflect this change.
The text was updated successfully, but these errors were encountered:
Fixes#2091. Fixes an issue where `performUpdate` was doing double duty as (1) make the element complete a pending update synchronously and (2) override to control update timing. Here `scheduleUpdate()` is added to satisfy (2), reserving (1) for `performUpdate()`. Since by default `scheduleUpdate()` just returns the value of `performUpdate()` this should not break any existing code. However, the docs are updated to recommend that for scheduling `scheduleUpdate()` be implemented in favor of `performUpdate()`.
Fixes#2091. Fixes an issue where `performUpdate` was doing double duty as (1) make the element complete a pending update synchronously and (2) override to control update timing. Here `scheduleUpdate()` is added to satisfy (2), reserving (1) for `performUpdate()`. Since by default `scheduleUpdate()` just returns the value of `performUpdate()` this should not break any existing code. However, the docs are updated to recommend that for scheduling `scheduleUpdate()` be implemented in favor of `performUpdate()`.
We currently have an issue where
performUpdate
is doing double duty. Users can override it to schedule updates, but we also recommend that users can call it to make an update synchronous. To resolve this, we'll addscheduleUpdate
and recommend users override that for scheduling and useperformUpdate
to make the update "go" synchronously.We also need to update the docs on lit.dev to reflect this change.
The text was updated successfully, but these errors were encountered: