3 ms·
In my experience this turns to nightmare when (not if, when) there is need to make changes to the libraries and app at the same time. Especially with libraries
by dezgeg 2y ago
In my experience this turns to nightmare when (not if, when) there is need to make changes to the libraries and app at the same time. Especially with libraries it's often necessary to create a client for an API at the same time to really know that the interface is any good.
- magicalhippo 2y agoThe idea is that the libraries we put in nuget are really non-project-specific. We'll use nuget to manage library versions rather than git submodules, so hopefully they can live fine in a separate repo. So updating them at the same time shouldn't be a huge deal, we just make the change in the library, publish the nuget package, and then bump the version number in the downstream projects that need the change. Ideally changes to these libraries should be relatively limited. For things that are intertwined, like an API client alongside the API provider and more project-specific libraries, we'll keep those together in the same repo. If this is what you're thinking of, I'd be interested in hearing more about your negative experiences with such a setup.