Improve ergonomics for observedAttributes/liveAttributes in Class mode #1

New issue

Open

opened 2026-01-07 15:10:11 +00:00 by endeavorance · 0 comments

endeavorance commented

2026-01-07 15:10:11 +00:00

Owner

This is not bad when using the factory, but when extending the Component class directly, you need to specify names of attributes in two places for reactive behavior to work properly.

The primary issue is avoiding the use of a MutationObserver (slower than observedAttributes) while still having type safety on liveAttributes which is a class property and not a static property so that it can access the class state shape generic.

This is not bad when using the factory, but when extending the Component class directly, you need to specify names of attributes in two places for reactive behavior to work properly. The primary issue is avoiding the use of a MutationObserver (slower than observedAttributes) while still having type safety on liveAttributes which is a class property and not a static property so that it can access the class state shape generic.