Question: How to deal with local state affecting the view?

[winterscar]

Hi! I like this project, and after having played around with it, a lot of the decisions make sense.

However, there's one thing I'm struggling to wrap my head around: How to deal with 'local' state affecting the rendered page.

Two examples from the data-star docs:

https://data-star.dev/examples/active_search
https://data-star.dev/examples/lazy_tabs

Both of those examples use @get() requests + signal values to partially update the UI state.

How would you replicate that in hyperlith?

[Ramblurr]

Any signals you define in your fragments should probably be using __ifmissing as the docs mention. I think that part of the readme could be improved.

Another way to say it is:

Any signals you define in the dom using a data- attribute should have __ifmissing otherwise the next render will come down and change their values.

[winterscar]

I think my question may have been unclear, sorry about that.

Consider the active_search example above. When the user types in the search box, in hyperlith, how should the application inform the back-end of the user's current search query, so that on the next re-render, the correct results are rendered?

One implementation might be to maintain an ephemeral user state atom that captures such values (or, for example what tab the user is currently on). That way, the main page renderer can look into that atom (for the current session) and render the expected search results.

Does that make any more sense?

[Ramblurr]

I think I understand your question now.

Yes, your idea of using an atom works. I use an atom that tracks state per tab. Look at the tab-state ns over in https://github.com/Ramblurr/hifi-crud/

I've implemented active search using exactly that, plus some other helpers for putting the state in the query string. I will see if I can add that to the hifi-crud demo.

@andersmurphy would probably say to put thay state in the database which is also a valid approach.

[winterscar]

Thanks, I appreciate the guidance!

[winterscar]

And thanks for that great HIFI CRUD readme. Lots of interesting stuff and opinions there too.

[Ramblurr]

And thanks for that great HIFI CRUD readme. Lots of interesting stuff and opinions there too.

🙏

Keep am eye on the repo, I've got lots of new stuff coming for it.