Skip to content

fix(deps): update dependency typeorm to v0.3.17 #139

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

fix(deps): update dependency typeorm to v0.3.17 #139

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Feb 8, 2023 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
typeorm (source) 0.2.45 -> 0.3.17 age adoption passing confidence

Release Notes

typeorm/typeorm (typeorm)

v0.3.17

Compare Source

Bug Fixes

v0.3.16

Compare Source

Bug Fixes
Features
Reverts

v0.3.15

Compare Source

Bug Fixes
  • make cache optional fields optional (#​9942) (159c60a)
  • prevent unique index identical to primary key (all sql dialects) (#​9940) (51eecc2)
  • SelectQueryBuilder builds incorrectly escaped alias in Oracle when used on entity with composite key (#​9668) (83c6c0e)
Features

v0.3.14

Compare Source

Bug Fixes
  • drop xml & yml connection option support. Addresses security issues in underlying dependency (#​9930) (7dac12c)
Features

v0.3.13

Compare Source

Bug Fixes
Features

v0.3.12

Compare Source

Bug Fixes
Features

v0.3.11

Compare Source

Fixes
Features

v0.3.10

Compare Source

Bug Fixes
Features

v0.3.9

Compare Source

v0.3.8

Compare Source

Bug Fixes
Features

v0.3.7

Compare Source

Bug Fixes
Features
Performance Improvements

v0.3.6

Compare Source

Features

v0.3.5

Compare Source

Bug Fixes

v0.3.4

Compare Source

Bug Fixes
Features

v0.3.3

Compare Source

Bug Fixes
  • improve initialization of custom repository (#​8782) (52a641c)
  • resolve entities correctly in datasource when globs are specified (#​8778) (a641c5d)
Features

v0.3.2

Compare Source

Bug Fixes
Features
Reverts

v0.3.1

Compare Source

Bug Fixes
Features
Reverts

v0.3.0

Compare Source

Changes in the version includes changes from the next branch and typeorm@next version.
They were pending their migration from 2018. Finally, they are in the master branch and master version.

Features

  • compilation target now is es2020. This requires Node.JS version 14+

  • 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 to DataSource.
    Old Connection 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 on find* methods and QueryBuilder. Value can be set to join or query.

    • join - loads relations using SQL JOIN expression
    • query - executes separate SQL queries for each relation

Default is join, but default can be set in ConnectionOptions:

createConnection({
    /* ... */
    relationLoadStrategy: "query"
})

Also, it can be set per-query in find* methods:

userRepository.find({
    relations: {
        photos: true
    }
})

And QueryBuilder:

userRepository
    .createQueryBuilder()
    .setRelationLoadStrategy("query")

For queries returning big amount of data, we recommend to use query strategy,
because it can be a more performant approach to query relations.

  • added new findOneBy, findOneByOrFail, findBy, countBy, findAndCountBy methods to BaseEntity, EntityManager and Repository:
const users = await userRepository.findBy({
    name: "Michael"
})

Overall find* and count* method signatures where changed, read the "breaking changes" section for more info.

  • new select type signature in FindOptions (used in find* methods):
userRepository.find({
    select: {
        id: true,
        firstName: true,
        lastName: true,
    }
})

Also, now it's possible to specify select columns of the loaded relations:

userRepository.find({
    select: {
        id: true,
        firstName: true,
        lastName: true,
        photo: {
            id: true,
            filename: true,
            album: {
                id: true,
                name: true,
            }
        }
    }
})
  • new relations type signature in FindOptions (used in find* methods):
userRepository.find({
    relations: {
        co

</details>

---

### Configuration

📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied.

♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 **Ignore**: Close this PR and you won't be reminded about this update again.

---

 - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box

---

This PR has been generated by [Mend Renovate](https://www.mend.io/free-developer-tools/renovate/). View repository job log [here](https://developer.mend.io/github/Magickbase/neuron).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC4xMjQuMiIsInVwZGF0ZWRJblZlciI6IjM2LjguMTEiLCJ0YXJnZXRCcmFuY2giOiJkZXZlbG9wIn0=-->

@renovate renovate bot force-pushed the renovate/typeorm-0.x branch from 228483f to 2a7e83a Compare February 13, 2023 02:46
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch from 2a7e83a to fd32e27 Compare March 7, 2023 08:43
@yanguoyu
Copy link

yanguoyu commented Mar 7, 2023

Many test cases run failed, so we need to upgrade it manually.

@renovate renovate bot changed the title fix(deps): update dependency typeorm to v0.3.12 fix(deps): update dependency typeorm to v0.3.12 - autoclosed Apr 4, 2023
@renovate renovate bot closed this Apr 4, 2023
@renovate renovate bot deleted the renovate/typeorm-0.x branch April 4, 2023 00:28
@renovate renovate bot changed the title fix(deps): update dependency typeorm to v0.3.12 - autoclosed fix(deps): update dependency typeorm to v0.3.12 Apr 4, 2023
@renovate renovate bot reopened this Apr 4, 2023
@renovate renovate bot restored the renovate/typeorm-0.x branch April 4, 2023 06:57
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch 2 times, most recently from 0b217ce to 1cf62cc Compare April 5, 2023 15:15
@yanguoyu yanguoyu mentioned this pull request Apr 6, 2023
Closed
4 tasks
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch from 1cf62cc to 7338bbc Compare April 6, 2023 11:20
@renovate renovate bot changed the title fix(deps): update dependency typeorm to v0.3.12 fix(deps): update dependency typeorm to v0.3.13 Apr 6, 2023
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch from 7338bbc to a0b2678 Compare April 9, 2023 08:03
@renovate renovate bot changed the title fix(deps): update dependency typeorm to v0.3.13 fix(deps): update dependency typeorm to v0.3.14 Apr 9, 2023
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch 3 times, most recently from acae8b6 to 79f29b6 Compare April 15, 2023 14:58
@renovate renovate bot changed the title fix(deps): update dependency typeorm to v0.3.14 fix(deps): update dependency typeorm to v0.3.15 Apr 15, 2023
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch from 79f29b6 to aefc630 Compare April 17, 2023 10:09
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch from aefc630 to 46ff18b Compare May 9, 2023 20:01
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch 2 times, most recently from e6cd074 to 61a2252 Compare June 20, 2023 09:18
@renovate renovate bot changed the title fix(deps): update dependency typeorm to v0.3.16 fix(deps): update dependency typeorm to v0.3.17 Jun 20, 2023
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch from 61a2252 to da5cdb0 Compare June 20, 2023 23:10
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch from da5cdb0 to 603a6e2 Compare June 21, 2023 10:43
@Keith-CY Keith-CY force-pushed the develop branch 2 times, most recently from b8e6d3c to 31dd4da Compare June 26, 2023 07:50
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch 2 times, most recently from 1d83c5a to 240260d Compare June 26, 2023 11:34
@pull-request-quantifier-deprecated
Copy link

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details 

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

  • Fast and predictable releases to production:
    • Optimal size changes are more likely to be reviewed faster with fewer
      iterations.
    • Similarity in low PR complexity drives similar review times.
  • Review quality is likely higher as complexity is lower:
    • Bugs are more likely to be detected.
    • Code inconsistencies are more likely to be detected.
  • Knowledge sharing is improved within the participants:
    • Small portions can be assimilated better.
  • Better engineering practices are exercised:
    • Solving big problems by dividing them in well contained, smaller problems.
    • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

  • Use the PullRequestQuantifier to quantify your PR accurately
    • Create a context profile for your repo using the context generator
    • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
    • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
    • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
  • Change your engineering behaviors
    • For PRs that fall outside of the desired spectrum, review the details and check if:
      • Your PR could be split in smaller, self-contained PRs instead
      • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

  • One line was added: +1 -0
  • One line was deleted: +0 -1
  • One line was modified: +1 -1 (git diff doesn't know about modified, it will
    interpret that line like one addition plus one deletion)
  • Change percentiles: Change characteristics (addition, deletion, modification)
    of this PR in relation to all other PRs within the repository.

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

@renovate renovate bot force-pushed the renovate/typeorm-0.x branch 2 times, most recently from 0fc6ec8 to 9052d77 Compare June 28, 2023 15:26
@Keith-CY Keith-CY force-pushed the develop branch 3 times, most recently from 6430710 to f2f5708 Compare June 28, 2023 18:02
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch 3 times, most recently from 48eeade to b144905 Compare July 3, 2023 01:33
@Keith-CY Keith-CY force-pushed the develop branch 2 times, most recently from c088e1e to 54c5f67 Compare July 20, 2023 05:51
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch 2 times, most recently from 25096c8 to cb1da2f Compare July 21, 2023 07:52
@renovate renovate bot force-pushed the renovate/typeorm-0.x branch from cb1da2f to ffd994a Compare September 7, 2023 02:52
@Keith-CY Keith-CY closed this Sep 7, 2023
@Keith-CY Keith-CY deleted the renovate/typeorm-0.x branch September 7, 2023 06:44
@renovate
Copy link
Author

renovate bot commented Sep 7, 2023 •
edited
Loading

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (0.3.17). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@alexsupa597 alexsupa597 alexsupa597 approved these changes

@Cedar67 Cedar67 Awaiting requested review from Cedar67

@Keith-CY Keith-CY Awaiting requested review from Keith-CY

@yanguoyu yanguoyu Awaiting requested review from yanguoyu

Assignees
No one assigned
Labels
dependencies Extra Small renovate
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@yanguoyu @alexsupa597 @Keith-CY