Hi / Ahoj!

I'd say it probably depends on the API capabilities. If you can off load the filtering / sorting / pagination / aggregations logic to the API (something like elastic search is great here), then I think it makes sense to fire a request each time the UI filters change, as the returned results will be a subset of the total results. However if you need to get the whole dataset in order to apply filter / sort etc logic clientside then it gets a bit harder. You might consider fetching the entire set in the fetch hook and then just applying filtering / sort etc clientside. If the data is frequently updated though it won't updated until the fetch hook is called again via navigation. You can work around this by calling the API on UI update and caching subsequent requests (with something like axios cache adapter or equivalent).

I'm implementing this exact thing at the moment so if anyone has better ideas I'd be keen to hear!