Help wanted to understand splitting up design files.

[RedMarcher]

As you can see, the number and size of the services for a project have ballooned more than expected. In order to make it readable, I've decided to split it up into multiple packages. Unfortunately, now it seems linking up the packages to each other is very difficult. I've tried fixing the issue myself for a while now, so I would really appreciate if there was a method of solving these issues while still keeping things in separate packages.

[raphael]

I think the problem stems from the fact that there are two API definitions in the final set of files that make up the design package (I'm assuming goa gen is invoked on the top level design (design/api.go). The top level design API definition overrides the portal package one. I am not sure what the right semantic is for this project but there are multiple ways to resolve the issue:

1. Remove the API definition from the design/api.go file - and only use the one defined in portal
2. Remove the API definition from the portal package and move the security design to the top level package
3. Create a 3rd file containing the API definition imported by both design/api.go and portal/api.go.

[RedMarcher]

I followed approach #1 and it worked. Not only did it solve the issue, it also allows me to compile the portal and microservice API separately, which is what I wanted from the beginning. Thank you so much.