[BUG] type metadata

Describe the bug

Type introspection doesn’t seem to work on types extending other types. Also, since types don’t support decorators (i.e. @reflected), one has to manually write getType<TypeA>() in order to activate metadata generation for TypeA. Without this, the result contains invalid values, like “type.name : ‘unknown’”

The code causing the problem

type TypeA = {
	prop1: string
}

type TypeB = TypeA & {
  prop2: string,
  prop3: string
}

const t0: Type = getType<TypeA>();
const t1: Type = getType<TypeB>();
console.log(t1.getProperties())

To Reproduce Steps to reproduce the behavior:

1. Build,
2. run,
3. see error…

Expected behavior All properties including inherited ones should be displayed by console.log(t1.getProperties())

Runtime (please complete the following information):

• Node.js version: v18.10.0
• TypeScript version: 4.8.4
• Compiler: [ttypescript]
• Bundler: [none]

Additional context

[uplight-dev]

Looking forward to it! And thanks for this awesome lib, makes a difference for my use case!

[Hookyns]

Okay, got it.

Sadly, this is intended behavior in the current version. This was intended as an optimisation, so only required types are reflected because of size of metadata (it would be megabytes for some projects). Type.find() was introduced later, but it is limited to reflected types.

New major version (alpha release is rly close) works in a different way (based on include/exclude options) so it works properly there.