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
Right now the web-components mix rendering logic and state.
Most importantly, we use a mix of signals, dom reaching, to propagate state and it's quite messy (no clear pattern).
Also we also rely a lot on mixins which is sometimes hard to follow (composition can be better).
We could have some state objects, like the search (query / result), the facets and each facets, etc.
Those states have to be handled by "search_name". Each state lives in it's own module and a get_xxx_state(search_name) function exist in each, it handle the fact that if search_name is null or '', it means "search-a-licious" (default name)
State objects have the advantage that they handle state propagation by themselves, so it could be really a good help.
The text was updated successfully, but these errors were encountered:
Right now the web-components mix rendering logic and state.
Most importantly, we use a mix of signals, dom reaching, to propagate state and it's quite messy (no clear pattern).
Also we also rely a lot on mixins which is sometimes hard to follow (composition can be better).
Investigate the use of https://www.npmjs.com/package/@lit-app/state to handle states.
We could have some state objects, like the search (query / result), the facets and each facets, etc.
Those states have to be handled by "search_name". Each state lives in it's own module and a get_xxx_state(search_name) function exist in each, it handle the fact that if search_name is null or '', it means "search-a-licious" (default name)
State objects have the advantage that they handle state propagation by themselves, so it could be really a good help.
The text was updated successfully, but these errors were encountered: