#JavaScript clean-up

Thanks for confirming and explaining!

Since I’m still getting comfortable with the codebase, I’ll try things out on my own first to better understand how this pattern works. I won’t assign the issue to myself just yet so that others can still pick it up if they’re ready to work on it.

That is, indeed, what I was imagining.

I'd probably start with some relatively low-hanging fruit, like, say, if the pageSize store value changes, it should automatically trigger a data reload (the load() function in ProjectBrowser.svelte).

Hi, I was going through this issue and wanted to confirm if my understanding is correct.

From what I gather, the goal is to reduce the need to pass event handler functions (like onFilterChange, onProjectSelect, etc.) down through multiple component levels. Instead of doing that, we should be using writable Svelte stores and directly subscribing to them in the components that need the data or need to respond to changes.

So for example, instead of passing a click handler from a parent component, we would set a value in a store like selectedProject, and any other component that needs to react would subscribe to that store.

Am I on the right track here? Also, are there any specific places in the current codebase where this refactor should be prioritized or where it's already partially implemented?

Thanks!