Skip to content

Releases: patmood/pocketbase-typegen

v1.1.5

26 Feb 23:20
0812864
Compare
Choose a tag to compare

What's Changed

Full Changelog: v1.1.4...v1.1.5

v1.1.4

08 Feb 05:52
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v1.1.3...v1.1.4

v1.1.3

22 Jan 16:47
883dc25
Compare
Choose a tag to compare

What's Changed

  • handle relation fields with maxSelect = null by @duytbp in #28
  • Support generics for expand fields by @patmood in #30

New Contributors

Full Changelog: v1.1.2...v1.1.3

v1.1.2

03 Dec 04:55
Compare
Choose a tag to compare

Fix select fields that use maxSelect > 1

v1.1.1

20 Nov 16:52
Compare
Choose a tag to compare

Fix enums for select fields that use special characters in values

v1.1.0

19 Nov 05:14
d04a445
Compare
Choose a tag to compare

Update the library to match changes in PocketBase v0.8

Versions

This will not be 100% backwards compatible with previous versions. System fields and URL based schema fetching will not work between versions.

When using PocketBase v0.8.x, use pocketbase-typegen v1.1.x

Users of PocketBase v0.7.x should use pocketbase-typegen v1.0.x

Every release is a painful reminder that I should have started at v0.0.1 and matched pocketbase version numbers...

Changelog

  • Add auth collection type system fields
  • Update system fields for all collections
  • Use enums for select fields
  • user field is deprecated
  • Update login URL (thanks @o2dependent !)
  • Introduce linting, formatting, and integration tests for the repo

v1.0.13

07 Nov 18:26
Compare
Choose a tag to compare

First release via GitHub.

Outputted types include:

  • Collections An enum of all collections
  • [CollectionName]Record One type for each collection (eg ProfilesRecord)
  • [CollectionName]Response One response type for each collection (eg ProfilesResponse) which includes system fields. This is what is returned from the PocketBase API.
  • CollectionRecords A type mapping each collection name to the record type