Say I have 3 packages A , B and C
B connects to data repository 1 and has features specific to this API.
C connects to data repository 2 and has features specific to this API.
In the end there will be a few more child packages.
Package A will have generic methods and other common functions (such as authentication) that apply to data received through B and C The rationale here is that it will be a more ordered way to keep up with development (for example, you would need to update one auth function, and not do it inside each child package). Therefore, for A it makes sense to be in the list of dependencies for B and C
But I would also like users to just install A and get access to all the child packages. To do this, I want B and C be on a list that depends on it.
Is it possible? Should I have a better workflow?
source share