We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
created
updated
Describe the bug Types for View collections are generated with created and updated, while View collections do not require or enforce those fields.
Example View collection Response:
{ "id": "RECORD_ID", "collectionId": "dxgefcmqccxee01", "collectionName": "shifts", "user": "RELATION_RECORD_ID", "clockIn": "RELATION_RECORD_ID", "clockOut": "RELATION_RECORD_ID" }
Generated Response type:
export type ShiftsResponse<Texpand = unknown> = Required<ShiftsRecord> & BaseSystemFields<Texpand>
BaseSystemFields includes created and updated so ShiftsResponse ends up with those fields.
I'm using env generation (pocketbase-typegen --env)
pocketbase-typegen --env
Versions pocketbase-typegen version: 1.2.1 pocketbase version: 0.19.3
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Types for View collections are generated with
created
andupdated
, while View collections do not require or enforce those fields.Example View collection Response:
Generated Response type:
BaseSystemFields includes
created
andupdated
so ShiftsResponse ends up with those fields.I'm using env generation (
pocketbase-typegen --env
)Versions
pocketbase-typegen version: 1.2.1
pocketbase version: 0.19.3
The text was updated successfully, but these errors were encountered: