0.27.1: fields with undefined values present in args of generated types about typegraphql-prisma HOT 8 CLOSED

@MichalLytek i believe this may be due to changing the generator's target to es2022 here

i've been playing around locally, and changing that one line creates these two different class definitions in the emitted js:

es2019

let FindManyUserArgs = class FindManyUserArgs {
};

es2022

let FindManyUserArgs = class FindManyUserArgs {
    where;
    orderBy;
    cursor;
    take;
    skip;
    distinct;
};

If I understand correctly, before ES2022, classes had to define properties in the constructor, but since the generated classes in type-graphql don't have constructors, they don't get initialized just by creating an instance of the class (and therefore don't exist unless typegraphql core sets a value for them? guessing here)

from typegraphql-prisma.

I don't see anything that could affect that:

What is your type-graphql version?

from typegraphql-prisma.

@MichalLytek here's the package.json with all the versions used in my repro

"type-graphql": "2.0.0-beta.4"

but i can also repro with 2.0.0-beta.3 and 2.0.0-beta.2

from typegraphql-prisma.

@MichalLytek it does seem the test snapshots were updated to expect all these undefined values in this commit

from typegraphql-prisma.

but i can also repro with 2.0.0-beta.3 and 2.0.0-beta.2

So this is related to type-graphql core itself. Will check it.

from typegraphql-prisma.

@MichalLytek #435

from typegraphql-prisma.

Closing as fixed by 4c053cc

from typegraphql-prisma.

Thank you @MichalLytek ! Much appreciated.

from typegraphql-prisma.