Using single vs multiple code repos for different workshop components?

If one is building workshop object views in the same ontology that then need to be deployed via marketplace to other spaces, what’s the better approach to use between:

  1. Having all supporting foundry functions in a single repository for all object views, or
  2. Having dedicated repository for each workshop object view

Workshop object view in this instance could also represent any sufficiently complex workshop application. Note some of the foundry functions related to some workshop apps could experience more frequent updates than others.

Hey @JulioM,

Both approaches have their merits, but I personally prefer having all functions of the same ontology / use case in a single repository. This approach provides a better overview and centralized management. However, others might have different opinions here.

Hope that helps.

Thanks, I share the same sentiment but I have wondered about the impact of shipping the code repository with the other unrelated functions within it. Or perhaps it only ships the deployed related function that’s used in the workshop app