nestjs-cqrs-starter
nestjs-cqrs-starter copied to clipboard
chore(deps): bump typeorm from 0.2.45 to 0.3.0
Bumps typeorm from 0.2.45 to 0.3.0.
Release notes
Sourced from typeorm's releases.
0.3.0
Changes in the version includes changes from the
next
branch andtypeorm@next
version. They were pending their migration from 2018. Finally, they are in the master branch and master version.Features
compilation
target
now ises2020
. This requires Node.JS version14+
TypeORM now properly works when installed within different node_modules contexts (often happen if TypeORM is a dependency of another library or TypeORM is heavily used in monorepo projects)
Connection
was renamed toDataSource
. OldConnection
is still there, but now it's deprecated. It will be completely removed in next version. New API:export const dataSource = new DataSource({ // ... options ... })
// load entities, establish db connection, sync schema, etc. await dataSource.connect()
Previously, you could use
new Connection()
,createConnection()
,getConnectionManager().create()
, etc. They all deprecated in favour of new syntax you can see above.New way gives you more flexibility and simplicity in usage.
- new custom repositories syntax:
export const UserRepository = myDataSource.getRepository(UserEntity).extend({ findUsersWithPhotos() { return this.find({ relations: { photos: true } }) } })
Old ways of custom repository creation were dropped.
added new option on relation load strategy called
relationLoadStrategy
. Relation load strategy is used on entity load and determines how relations must be loaded when you query entities and their relations from the database. Used onfind*
methods andQueryBuilder
. Value can be set tojoin
orquery
.
join
- loads relations using SQLJOIN
expression
... (truncated)
Changelog
Sourced from typeorm's changelog.
0.3.0 (2022-03-17)
Changes in the version includes changes from the
next
branch andtypeorm@next
version. They were pending their migration from 2018. Finally, they are in the master branch and master version.Features
compilation
target
now ises2020
. This requires Node.JS version14+
TypeORM now properly works when installed within different node_modules contexts (often happen if TypeORM is a dependency of another library or TypeORM is heavily used in monorepo projects)
Connection
was renamed toDataSource
. OldConnection
is still there, but now it's deprecated. It will be completely removed in next version. New API:export const dataSource = new DataSource({ // ... options ... })
// load entities, establish db connection, sync schema, etc. await dataSource.connect()
Previously, you could use
new Connection()
,createConnection()
,getConnectionManager().create()
, etc. They all deprecated in favour of new syntax you can see above.New way gives you more flexibility and simplicity in usage.
- new custom repositories syntax:
export const UserRepository = myDataSource.getRepository(UserEntity).extend({ findUsersWithPhotos() { return this.find({ relations: { photos: true, }, }) }, })
Old ways of custom repository creation were dropped.
- added new option on relation load strategy called
relationLoadStrategy
. Relation load strategy is used on entity load and determines how relations must be loaded when you query entities and their relations from the database. Used onfind*
methods andQueryBuilder
. Value can be set tojoin
orquery
.
... (truncated)
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebase
will rebase this PR -
@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it -
@dependabot merge
will merge this PR after your CI passes on it -
@dependabot squash and merge
will squash and merge this PR after your CI passes on it -
@dependabot cancel merge
will cancel a previously requested merge and block automerging -
@dependabot reopen
will reopen this PR if it is closed -
@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency -
@dependabot ignore this major version
will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor version
will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.