I may have something like this in my project.
I use a component that holds the logic for a list. For example, I have a file browser, that uses parameters to fetch the files in this (Project or folder). Instead of using collection to hold this I am actually calling it a single time in the workflow and storing the data inside the component.
When the component loads, it takes in ie. project_id and calls the function to get the correct data.
I use Supabase, so for me it is SELECT (with filter: project_id = X, for example) and then i return all rows, and store them in a component variable.
This variable is used to display the list.
This way, its really easy to seperate the variables since its inside the component.
This way you can also have several of the same components on the same page, and each component just calls whatever filter you need it to.
The call to supabase and storing variable:
Display the response in list:
