I regularly work across multiple projects that are inter-related.

Lets say that I have project A and project B.

Project B depends on project A.

The code for both projects are on my local machine.

To create a release of project B I have to change my pubspec to pull Project A from pub.dev (rather than a local path).

This is fine.

The problem is if I forget to move the pubspec dependency for Project A back to a local path.

So the scenario is:

I'm working happily in Project B within vscode.
I control-click through a method that is in Project A.
If find a problem in Project A and start editing the code.

The problem is that the code in Project A is being pulled from .pub-cache.

Whilst dart-code does provide a warning about editing in a external folder I ignore this message because I'm assuming that its just due to the local path to project A.

What I would like to see is that if you open a file in .pub-cache then vscode should make the code non-editable and ideally the notification dialog should be in a more aggressive colour such as red.