hillin

Take a look at this example: ```csharp public class TestDto { public int? OptionalInt { get; set; } public int NonNullInt { get; set; } public required int RequiredInt {...

@sumeyyeKurtulus no they are **not** the same.

Worklets are so niche (at least for now) that I don't think it would ever get the required upvotes. However since Angular already have the [support for service workers](https://github.com/angular/angular-cli/blob/8bc43bcdf594b77ea88e0fe33217e801f8bcee42/packages/angular/build/src/tools/angular/transformers/web-worker-transformer.ts) and...

> Although the property allows `null` values, the backend needs it to be `non-null` @maliming I don't quite get this one, why it must be non-null? Please check out the...

Shouldn't `age2: null, name2: null` be specified in the payload (④)? I think `null` and `undefined` should be distinguishedly used: `undefined` for omitting a field (not required), while `null` can...

I guess the validation system should also treat `undefined` and `null` differently? Is it possible?

Then I guess we have to comply to this behavior, but there still can be improvements to be made. In short, we only generate non-required, non-nullable fields as optional: ```csharp...

> Can be null in client *Client* as in, **.HttpApi.Client** project? > Must be in request Must **not be null** in request, if I understand correctly? > public bool IsNullable...

> This means you can set this property to null in your Angular client. Nullable in backend. Do you mean: `class Dto { public required string? Value }` → `interface...

I believe this is the relevant bug in MySql.EntityFrameworkCore: https://bugs.mysql.com/bug.php?id=119461