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
Savvy users know that the @query decorator crawls the DOM on each access looking for a matching element. If these users are concerned about performance, they are inclined to access the property once and memoize it into another property. This kind of defeats the purpose of having the property in the first place.
However, sometimes it's important that the result of is dynamic. We can address both use cases by adding a caching option to the decorator, something like @query({cache: true}).
Acceptance criteria
Enhancement landed.
The text was updated successfully, but these errors were encountered:
Description
Savvy users know that the
@query
decorator crawls the DOM on each access looking for a matching element. If these users are concerned about performance, they are inclined to access the property once and memoize it into another property. This kind of defeats the purpose of having the property in the first place.However, sometimes it's important that the result of is dynamic. We can address both use cases by adding a caching option to the decorator, something like
@query({cache: true})
.Acceptance criteria
Enhancement landed.
The text was updated successfully, but these errors were encountered: