Workspace level importMap breaks member import entry resolution

[Yohe-Am]

What it says on the tin, the entries on the workspace member import map don't work if there's an importMap entry on the workspace root config. The error displayed is the good old:

error: Relative import path "@two/mod.ts" not prefixed with / or ./ or ../ and not in import map from "file:///tmp/repro/one/mod.ts"
    at file:///tmp/repro/one/mod.ts:1:23

This breaks the behavior described by the docs.

Exclusive with imports and scopes per config file. It is allowed to have importMap in the workspace config, and imports in the package config.

Unless I'm reading them anyways. This only happens from the 0.2.5 onwards.

Reproduction avail here.

[dsherret]

This is by design. It's a scenario we don't support because we found it's too hard to reason exactly how this should work in every scenario. You need to move the import map into the deno.json or put everything in the import map. We should be displaying a warning in this scenario though.