In a situation with two packages named similarly:
- Partas.Solid.ZagJs
- Glutinum.ZagJs
The name difference derives from the fact that Glutinum.ZagJs is supposed to be agnostic of Partas.Solid
The default scoping scheme assesses both as ZagJs.
While I could use the scoping function to match for this case and change it, it would be a boon if this occured by default. Perhaps an initial prefix for the scope based on the preceding chunk of the project file name?
In a situation with two packages named similarly:
The default scoping scheme assesses both as ZagJs.
While I could use the scoping function to match for this case and change it, it would be a boon if this occured by default. Perhaps an initial prefix for the scope based on the preceding chunk of the project file name?