-
|
Let's get a simple "Users" collection from the "auth" example: it contains generated types for the "Users" collection here: export interface UsersSelect<T extends boolean = true> {
firstName?: T;
lastName?: T;
roles?: T;
updatedAt?: T;
createdAt?: T;
email?: T;
resetPasswordToken?: T;
resetPasswordExpiration?: T;
salt?: T;
hash?: T;
loginAttempts?: T;
lockUntil?: T;
}There are all defined fields listed, but the Is this intentional and we should add the id field to this type manually for such cases, or a bug? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Yes this is intentional because the |
Beta Was this translation helpful? Give feedback.
Yes this is intentional because the
idfield is always selected.