typeorm-polymorphic
typeorm-polymorphic copied to clipboard
bashleigh
Typeorm polymorphic relationship management
Bumps [word-wrap](https://github.com/jonschlinkert/word-wrap) from 1.2.3 to 1.2.4. Release notes Sourced from word-wrap's releases. 1.2.4 What's Changed Remove default indent by @mohd-akram in jonschlinkert/word-wrap#24 🔒fix: CVE 2023 26115 (2) by @OlafConijn in...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Bumps [semver](https://github.com/npm/node-semver) from 5.7.1 to 5.7.2. Release notes Sourced from semver's releases. v5.7.2 5.7.2 (2023-07-10) Bug Fixes 2f8fd41 #585 better handling of whitespace (#585) (@joaomoreno, @lukekarrys) Changelog Sourced from semver's...
Bumps [tough-cookie](https://github.com/salesforce/tough-cookie) from 4.1.2 to 4.1.3. Release notes Sourced from tough-cookie's releases. 4.1.3 Security fix for Prototype Pollution discovery in #282. This is a minor release, although output from the...
How to implement nullable relationship? I'm implementing this package with NestJS, all work fine except quering when relationship is null. Entity schema: ``` @Entity({ name: 'businesses', }) export class Business...
user.entity.ts ``` @PolymorphicChildren(() => Media, { eager: true, }) media: Media[]; ``` media.entity.ts ``` @PolymorphicParent(() => [User]) owner: User; @Column({ length: 191, nullable: true }) entityType: string; @Column({ nullable: true...
`entityTypeId` is obviously a typo.
I added `PolymorphicParent` and `PolymorphicChildren` decorators to entities but when i try to generate migration like this ``` typeorm-ts-node-esm migration:generate -d src/migrations-data-source.ts src/migrations/$PG_MIGRATION_NAME ``` and my migrations generated without new...
how i can use @PolymorphicRepository decorator into entity.service.ts file? ` @InjectRepository(Like) @PolymorphicRepository(Like) private readonly likeRepository: AbstractPolymorphicRepository, ` that not work, help please
…om polymorphic child Before, on a child repository's options, we didn't handle the case in which there were multiple parents which had different `primaryColumn` names Now we take such configurations...
