Link could ignore names or files from a specified list or of a particular nameclass

[rikedyp]

Is your feature request related to a problem? Please describe.
After linking my project, if I import a tool to the same namespace and either intentionally or accidentally modify it, then I get a copy of the tool in my project source which I have to subsequently delete or .gitignore or whatever. This is particularly relevant if I link my project to the root namespace #.

Describe the solution you'd like
Some configuration parameter could be a list of either/or a combination of names, file paths, nameclasses and/or file extensions for link to ignore.

Describe alternatives you've considered
Everyone must always keep their projects modular and link/import each piece to a separate namespace.

[aplteam]

This can get out of hand pretty quickly, in particular when your project is #. Just one of the many reasons why this is not recommended.

If you put your project in a namespace like MyProject and you bring your tool (like MyTool) into # rather than your project than you can establish a ref like this:

#.MyProject.MyTool←#.MyTool

Now you can uses it in exactly the same way as if it was brought into #.MyProject but Link would ignore any changes to code in it.

That way you can achieve what you want without adding complexity to Link.

Putting your project into # is asking for trouble because whenever you bring something into your project there is a chance of a name clash.