Replies: 2 comments 1 reply
-
This is a pretty uncommon case so we don't have an option for this exact use case, but here are a few options to consider:
However, can you expand on why it is important for
|
Beta Was this translation helpful? Give feedback.
-
If the changed property is not used in Based on that understanding, can you try and answer this question again?
Lit is designed to use a very simple mechanism for triggering the update lifecycle: It creates accessors for each We currently don't have a way to separate the part of the update lifecycle that does attribute reflection from the part of the update lifecycle that does render based on individual property options, since that would introduce extra complexity for a level of optimization is rarely necessary. |
Beta Was this translation helpful? Give feedback.
-
For example. There has a component with an attribute named
theme
.theme
attribute is only used in css selector for the theme and click event.If I update theme property or attribute. The component always is trigger render. This is not what I expected.
I cannot found an option to prevent this.
I tried to use getter/setter instead of @Property decorator. It's works but so troublesome.
Beta Was this translation helpful? Give feedback.
All reactions