ID field is required

[alexvdvalk]

Currently the ID field is marked as required on all the types. This makes sense, but in cases where I'm creating a new item, I don't yet have an ID because i'm busy constructing the payload which will be sent to the directus API.

A suggestion is to make the ID field optional if directus is setup to auto-create a UUID or incremental ID.

[bryantgillespie]

This is an issue we've ran into before -- partly an upstream thing where the signature for the create method should not require a primary key but that would also mean we'd need a way to denote that it's a primary key in the types.

Do you see any gotchas or downsides to making the field optional?

[alexvdvalk]

In my use case, I'm constructing a payload with which I'll POST into Directus API, so the types are really useful here, but i had to use an

Omit<FormSubmissionValue, 'id'>

to omit the id, and then tried using a Partial to make all the properties optional, but this is not ideal.

Some tables also have manual Primary Key strings which would still be required.

I don't see any gotchas but i think i'll manually make all the IDs optional in my project and do some testing first.