Currently, there's basically no reason for service and repository classes to exist as two distinct layers—most service class methods are just forwarding repository method calls and there's no instance data which requires the use of a class.
Instead, there should be one unified composables layer that serves as a collection of free functions that can be imported a la carte, also improving performance since you only need to import what you use and don't need to instantiate a full class for every method call.
Most of the current code can be reused and simply converted into individually-exported functions, and different services and controllers can import from other files without fear of self dependence.
This will also help facilitate future issues since different collections will be able to interact with each other much more easily.
Currently, there's basically no reason for service and repository classes to exist as two distinct layers—most service class methods are just forwarding repository method calls and there's no instance data which requires the use of a class.
Instead, there should be one unified composables layer that serves as a collection of free functions that can be imported a la carte, also improving performance since you only need to import what you use and don't need to instantiate a full class for every method call.
Most of the current code can be reused and simply converted into individually-exported functions, and different services and controllers can import from other files without fear of self dependence.
This will also help facilitate future issues since different collections will be able to interact with each other much more easily.