Generated models have optional properties when defined as required in schema

[devklick]

In my schema.prisma I have a model defined with what I understand to be a required field, since it's not using the optional modifier:

model Person {
  id   Int    @id @default(autoincrement())
  name String @db.VarChar(60)
}

I've run the generator as per the docs, with:

npx prisma generate

But the generated Person class has both the id and name properties as being optional:

class Person {
  const Person({
    this.id,
    this.name,
  });

  factory Person.fromJson(Map json) => Game(
        id: json['id'],
        name: json['name'],
      );

  final int? id;

  final String? name;
}

Is this the intended behaviour or have I missed something?

Using version 4.0.0-beta.3

[medz]

This is the expected behavior. All fields of model are optional fields. The main purpose is for me to adapt the select and include functions (for selecting only some fields or additional fields containing relationships)

[devklick]

@medz Thank you for clarifying.

Since this appears to be different behaviour to Prisma JS, it might be worth adding something in the model docs.

I'll close this issue as you've confirmed it's expected behaviour

[medz]

@devklick

Since this appears to be different behaviour to Prisma JS

Yes, since Prisma JS/TS relies on TS's type calculation, types can be constructed dynamically. Other languages do not have support for this feature. If you want to implement select/include, you can only use nullable types.