Question: pure frontend use case

[xabicasado]

Hi! I have one question regarding the convenient structure for pure frontend use cases:

If I want to filter data retrieved from the database on the client side, we wouldn't be talking about a repository method. The readme clearly states that "Repositories are how we implement the database operations."

Which strategy should I follow for this case? Will it be an use case with no repository needed (maybe similar to this one), on which I directly filter the data received as a param, with a controller for the data validation and then call this controller on the page? Please correct me if I'm misunderstanding.

Thanks

[xabicasado]

Also, this solution will return the following Next.js error when I try to pass this controller as a prop to a client component that performs the search without calling a server action (which I don't think as the correct way to achieve it neither, because we are not talking about an async function):

Functions cannot be passed directly to Client Components unless you explicitly expose it by marking it with "use server".

Do you have any clue about which solution take for this case?

[nikolovlazar]

How are you obtaining your data on the client? It has to be through HTTP or other networking method. If so, that would be your repository.

The repository pattern does not mean that it will always interface with a database driver. It just means that it's responsible for obtaining the data, regardless of the way it's obtained. So in your case you'd still have a repository on the client side, but it's going to use fetch or any networking library you're using to obtain the data.

I should update the readme to reflect that, but in our case it's still true - repositories are how we implement the database operations.

As for filtering, you'd do that outside of your repository, either in a service if the filtering criteria is too complicated, or directly in your use case.

---

Functions cannot be passed directly to Client Components unless you explicitly expose it by marking it with "use server".

Regarding this issue, props in React are handled differently than regular function arguments, so it's best if you take a different approach. You can directly import the controller. I don't think the controller needs to be injected, so feel free to access it directly.

[xabicasado]

Maybe I didn't make myself clear on the first point. First I am obtaining on the server-side and the proceed to store it into a React context. Once its stored, I may want to filter it, but I already have the data.