Releases: samhuk/ts-pg-orm
Releases · samhuk/ts-pg-orm
v5.1.0
Summary
This version contains breaking changes. This minor version bump had 4 primary goals:
- Create a public API for the package so that users don't have to
importfrom nested directories withints-pg-orm/dist/... - Fix bug with related data properties not showing for
get()andgetMany()store functions. - Support for circular relations when provisioning and unprovisioning stores.
- Incremental quality improvements, e.g. less reliance on
@ts-ignore' and bettercreateRelation()` code.
New Features:
- Support for circular relations (this required a lot of changes to the store provisioning code).
Improvements:
- Reduce dependence on
@ts-ignoreand instead useAccess<T>andCast<T>"forcer generics". - Providing a simplified single-level public API for all of the functions, enums, types, etc. that are required to use the package. This is at the root level
index.tsfile, so they are all easily accessible. - Fix a bug with 5.0.x where related data props were not included in
get()andgetMany()store functions due to how thenameproperty of theRelationtype was declared. - Ensure only absolutely required typescript is included in typescript dist directory (for npm publishing)
- Improve ts build npm commands
- Improvement in the
createRelation()code. - Etc.
v5.0.1
v5.0.0
V5 of ts-pg-orm primarily focuses on improving two areas:
- How data formats and relations are defined:
- Require less use of as const
- Make data type and sub-type names more terse
- (Generally make defining data formats and relations easier)
- Simplify the typing code of data formats and relations
- Improve the performance of typing code to make tsc compilation (=> intellisense) faster
- How stores are created, provisioned, and accessed.
V5 also refactors all of the core typing code to be simpler and more accessible (e.g. less use of vaguely-named generics like "I, J, K, L", etc.)
v4.3.2
4.3.1 and 4.3.2 have focused on various minor fixes and begins introducing some essential integration tests to cover data store functionality. These tests connect to a real postgresql database and runs some store functions with some assertions on the results.
v4.3.0
Existing store function changes:
- Rename
getSingletoget - Rename
getMultipletogetMany - Rename
updateSingletoupdate, and include handling for queries with and without LIMIT, OFFSET, and ORDER BY - Rename
deleteSingletodelete, and include handling for queries with and without LIMIT, OFFSET, and ORDER BY
New store functions:
existscount
Additionally, large store code organizational improvement and README simplification.