Is there a reason why it's restricted to only reference contract types in a direct dependency - rather than multiple levels? We allow this kind of nested referencing for a [link value] - but is there a reason why we shouldn't allow this for a deployment's contract type?
@pipermerriam It appears as though in V2 - a deployment can only refer to a contract type from a direct dependency.
Is there a reason why it's restricted to only reference contract types in a direct dependency - rather than multiple levels? We allow this kind of nested referencing for a [link value] - but is there a reason why we shouldn't allow this for a deployment's contract type?