v1.0.3

• [Rerelease from v1.0.2] update the generated Set type for resources with isBatchKeyASet: true to use type inference (fixes an incompatibility with dataloader-codegen and ts-reset)

v1.0.2

• update the generated Set type for resources with isBatchKeyASet: true to use type inference (fixes an incompatibility with dataloader-codegen and ts-reset)

v1.0.1

• Rerelease of v1.0.0 (fixes publish workflow)

v1.0.0

This release drops Flow support in favor of TypeScript - dataloaders will be now be generated with TypeScript types. To upgrade, make sure your codebase is in TypeScript and switch the typings.language key in your config file from 'flow' to 'typescript'.

Other changes:

• Bumps minimum Node version to 22.x (LTS)
• Fixes an issue where isBatchKeyASet would supply keys to the resource as an Array instead of a Set

v0.5.1

• Fix schema to support maxBatchSize (#353)

Release v0.5.0

This deploys the following:

• Add new option maxBatchSizing for batched requests (#351)
• Fix pipeline (#352)

v0.4.4

Fixes ordering of $NonMaybeType so it affects the batch property and not the element #341

v0.4.3

• Forces nullable batchKeys to be non-nullable (#339)

v0.4.2

• fixed a bug, separated getPropertyBatchLoader and getBatchLoader, so that flow won't throw errors for batch resources that don't have propertyBatch key (#329)

v0.4.1

add new config to batch properties calls (#299)