I chatted with guys about this - and it turns out that I was thinking of packages as if they were projects, however in reality we are waiting for a proper “project” model (this is what Cargo - who’s new name I’ve forgotten - is all about).
So I should promote my use of tags up to proper packages and for now “prefix” my packages with a project name. This might explain why when you create a unit test , it creates an automatic top level package (and not a tag), which has often confused me in the past. I’m still a bit unsure what tags would then be used for in a world with projects. But it seems that the guidance is to think projects / packages (not baseline/package/tags) Tim Sent from my iPhone > On 20 Apr 2019, at 00:15, Tim Mackinnon <tim@testit.works> wrote: > > Well I guess most usages are “load 3rd party baseline” and you don’t really > care who owns the extension methods (all the sub-tags are normally part of > the parent project anyway). > > If you do add any extensions to that project, you probably also don’t notice > they don’t show up in any tags of the classes you extend (only in the > containing project). It’s subtle but probably doesn’t affect execution, just > readability. > > Tim > > Sent from my iPhone > >> On 19 Apr 2019, at 18:10, Sean P. DeNigris <s...@clipperadams.com> wrote: >> >> If that's the case, this sounds like a huge problem. I'm surprised no one >> has reported it already. > >
