mock set to null when interface and namespace have the same name

Subject of the issue

When there is a namespace and an interface with the same name, with the namespace declared first, mocking that interface returns null.

Your environment

• ts-auto-mock version: 3.2.2
• typescript version: 4.3.2
• node version: 14.3.0
• npm version: 7.6.0
• list any other dependencies that you think are relevant
  • though it is probably irrelevant to the example, I am using jest-ts-auto-mock v2.0.0

Steps to reproduce

import {createMock} from 'ts-auto-mock'
namespace B {}
interface B {
  b: string
}
console.log(createMock<B>())

Expected behavior

Should log {b: ""}

Actual behavior

Actually logs null

[Pmyl]

PR open to fix it #793 now waiting for @uittorio to review it, in one day max it should go in 😄

[Pmyl]

I confirmed the bug, I’ll take care of it!

The last thing you said is normal, for the transformer B is an empty object so that generates an empty object (plus a marker for mocks to work that won’t impact any runtime execution)