robinck / typeorm-fixtures Goto Github PK

Hello,

There is a typo when calling methods in README.md. _call is used twice instead of __call.

I am trying to deploy my application into docker container and this package is breaking my deploy. I tried to configure docker container with DISABLE_OPENCOLLECTIVE=true and error persists.

The devDependency @types/lodash was updated from 4.14.140 to 4.14.141.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/lodash is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I have a makefile with a command:

db-sync: NODE_ENV=$(NODE_ENV) $(NPM_BIN)/fixtures --config ./ormconfig.js --sync --debug ./data/fixtures

When I run this code, I get:
Fail fixture loading: Unexpected token { (node:53075) UnhandledPromiseRejectionWarning: CannotExecuteNotConnectedError: Cannot execute operation on "default" connection because connection is not yet established. at new CannotExecuteNotConnectedError (/Users/marcio/Development/projects/personal/typescript-express-di-orm/node_modules/typeorm/error/CannotExecuteNotConnectedError.js:10:28) at Connection.<anonymous> (/Users/marcio/Development/projects/personal/typescript-express-di-orm/node_modules/typeorm/connection/Connection.js:173:35) at step (/Users/marcio/Development/projects/personal/typescript-express-di-orm/node_modules/tslib/tslib.js:136:27) at Object.next (/Users/marcio/Development/projects/personal/typescript-express-di-orm/node_modules/tslib/tslib.js:117:57) at /Users/marcio/Development/projects/personal/typescript-express-di-orm/node_modules/tslib/tslib.js:110:75 at new Promise (<anonymous>) at Object.__awaiter (/Users/marcio/Development/projects/personal/typescript-express-di-orm/node_modules/tslib/tslib.js:106:16) at Connection.close (/Users/marcio/Development/projects/personal/typescript-express-di-orm/node_modules/typeorm/connection/Connection.js:168:24) at Object.<anonymous> (/Users/marcio/Development/projects/personal/typescript-express-di-orm/node_modules/typeorm-fixtures-cli/dist/cli.js:111:37) at Generator.next (<anonymous>) (node:53075) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2) (node:53075) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Fun fact: I use the same configuration to run fixtures before my unit-tests programmatically and works well

ormconfig.js
{ "name":"default", "type":"mysql", "host":"127.0.0.1", "port":3306, "username":"blablabla", "password":"blablabla", "database":"blablabla", "ssl":false, "entityPrefix":"", "synchronize":true, "dropSchema":true, "logging":[ "query", "error", "schema", "warn", "info", "log" ], "extra":{ "ssl":false }, "autoSchemaSync":true, "entities":[ "./src/entities/*.*" ], "migrations":[ "./src/migrations/*.*" ], "subscribers":[ "./src/subscribers/*.*" ], "cli":{ "entitiesDir":"./src/entities", "migrationsDir":"./src/migrations", "subscribersDir":"./src/subscribers" } }

Do you guys have any idea what could be wrong? For me, this seems the fixture is trying to run before have a opened connection. But make no sense because all logic is inside the then of createConnection

I have installed this package following the documentation with:

npm install typeorm-fixtures-cli --save-dev

I also have created a fixture file in fixtures/User.yml with:

entity: User
items:
    user1:
        username: '[email protected]'

But when I try to run the fixtures command I get a command not found error

root@ed0c1271ba48:/application# fixtures
bash: fixtures: command not found

I am running this on a node:12.16.2 Docker image

Do I need to do anything else after installing the package?

Thank you very much.

If you have relations defined as lazy, i.e. like:

@Entity()
class User {
  @OneToOne('Profile', 'user')
  profile: Promise<Profile>
}

Then when you run fixtures - all relation fields are nulls.
No exceptions thrown during fixtures loading.

TypeOrm Lazy Relations doc: https://typeorm.io/#/eager-and-lazy-relations/lazy-relations

Your Environment

Your Environment

We have the following setup and when we run the fixtures we get pages of UnhandledPromiseRejectionWarning output. It seems to be related to bcryptjs. We have a target in a make file which calls a package.json script specifying which fixtures orm config file to use:

make file command that calls the package.json scirpt
npm run fixtures -- --config tests/ormconfig_docker-local.yml

package.json script
"fixtures": "rm -f .env && fixtures ./tests/fixtures --require=ts-node/register",

ormconfig_docker-local.yml

- name: default
  type: postgres
  host: database
  port: 5432
  database: xxx
  username: xxx
  password: xxx
  synchronize: false
  logging: false
  entities:
    - ./server/entities/**/*.ts
  cli:
    entitiesDir: ./server/entities

(node:33) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 4899)
(node:33) UnhandledPromiseRejectionWarning: Error: Illegal arguments: function, undefined
    at _async (/app/node_modules/bcryptjs/dist/bcrypt.js:214:46)
    at /app/node_modules/bcryptjs/dist/bcrypt.js:223:17
    at new Promise (<anonymous>)
    at User.bcrypt.hash (/app/node_modules/bcryptjs/dist/bcrypt.js:222:20)
    at Promise (internal/util.js:275:30)
    at new Promise (<anonymous>)
    at User._hashAsync (internal/util.js:274:12)
    at _loop_1 (/app/src/TransformOperationExecutor.ts:154:47)
    at TransformOperationExecutor.transform (/app/node_modules/class-transformer/TransformOperationExecutor.js:260:17)
    at _loop_1 (/app/src/TransformOperationExecutor.ts:246:43)
    at TransformOperationExecutor.transform (/app/node_modules/class-transformer/TransformOperationExecutor.js:260:17)
    at ClassTransformer.plainToClassFromExist (/app/src/ClassTransformer.ts:55:25)
    at Object.plainToClassFromExist (/app/src/index.ts:48:29)
    at Builder.<anonymous> (/app/node_modules/typeorm-fixtures-cli/src/Builder.ts:78:22)
    at Generator.next (<anonymous>)
    at /app/node_modules/typeorm-fixtures-cli/dist/Builder.js:7:71
    at new Promise (<anonymous>)
    at __awaiter (/app/node_modules/typeorm-fixtures-cli/dist/Builder.js:3:12)
    at Builder.build (/app/node_modules/typeorm-fixtures-cli/dist/Builder.js:26:16)
    at Function.loadFixtures (/app/tests/support/utils.ts:232:51)
    at process._tickCallback (internal/process/next_tick.js:68:7)�Á��

During installation of typeorm-fixtures-cli following warning is generated:

warning typeorm-fixtures-cli > [email protected]: This module has moved and is now available at @hapi/joi. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.

Is there a way to use as an API instead of CLI?

I upgraded to 1.4.0 and get a "Cannot find module 'joi' after upgrade to 1.4.0" error when running fixtures.
When searching for the usage of the removed dependency joi I find it in typeorm-fixtures-cli/dist/schema/jFixturesSchema.js and .../dist/Loader
The typeorm-fixtures-cli/package.json has the correct version of 1.4.0 though with @hapi/joi in dependencies.

It seems like the npm package ships with an old version of the source code.

I'm generating my fixtures programmatically and I'd like to use environment variables in fixtures like this: id: '<{process.env.ADMIN_USER_ID}>'. Currently I have to manually modify parameters like this:

  loader.load(path.resolve(__dirname, process.env.NODE_ENV));
  const configs = loader.fixtureConfigs;
  configs.forEach((cfg) => {
    if (cfg.entity === 'User') {
      set(cfg, 'cfg.parameters.userIds.admin', process.env.ADMIN_USER_ID);
    }
  });

It would be nice to have process.env added to parameters by default. I've looked at the sources and could not decide where it fits.

Hi. Thank you for this awesome project.
I'm trying to use it with nestjs for e2e testing and i keep getting this error.

TypeScript diagnostics (customize using `[jest-config].globals.ts-jest.diagnostics` option):
    test/test.utils.ts:113:11 - error TS2571: Object is of type 'unknown'.

    113           entity.constructor.name,
                  ~~~~~~
    test/test.utils.ts:114:17 - error TS2345: Argument of type 'unknown' is not assignable to parameter of type 'DeepPartial<{}>'.

    114         )).save(entity);

/test/test.utils.ts

import { Injectable } from "@nestjs/common";
import * as fs from "fs";
import * as path from "path";
import {
  Builder,
  fixturesIterator,
  Loader,
  Parser,
  Resolver,
} from "typeorm-fixtures-cli/dist";
import { DatabaseService } from "../src/database/database.service";

@Injectable()
export class TestUtils {
  databaseService: DatabaseService;

  constructor(databaseService: DatabaseService) {
    if (process.env.NODE_ENV !== "test") {
      throw new Error("ERROR-TEST-UTILS-ONLY-FOR-TESTS");
    }
    this.databaseService = databaseService;
  }

  async loadFixtures(fixturesPath: string) {
    const connection = await this.databaseService.connection;
    try {
      const loader = new Loader();
      loader.load(path.resolve("./fixtures/User.yml"));

      const resolver = new Resolver();
      const fixtures = resolver.resolve(loader.fixtureConfigs);
      const builder = new Builder(connection, new Parser());

      for (const fixture of fixturesIterator(fixtures)) {
        const entity = await builder.build(fixture);
        (await this.databaseService.getRepository(
          entity.constructor.name,
        )).save(entity);
      }
    } catch (err) {
      throw err;
    } finally {
      if (connection) {
        await connection.close();
      }
    }
  }
}

/src/database/database.service.ts

import { Injectable } from "@nestjs/common";
import { InjectConnection } from "@nestjs/typeorm";
import { Connection } from "typeorm";

@Injectable()
export class DatabaseService {
  constructor(@InjectConnection() public connection: Connection) {}

  async getRepository<T>(entity) {
    return this.connection.getRepository(entity);
  }
}

/test/fixtures/User.yml

entity: User
items:
  user1:
    name: '{{name.firstName}}'
    email: '{{internet.email}}'
    password: 'password',
  user2:
    name: '{{name.firstName}}'
    email: '{{internet.email}}'
    password: 'password',

Any help would be appreciated!

There have been updates to the commitlint monorepo:

• • The devDependency @commitlint/cli was updated from 8.0.0 to 8.1.0.

• The devDependency @commitlint/config-conventional was updated from 8.0.0 to 8.1.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the commitlint group definition.

commitlint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

It would be very nice to be able to set references in the processor to allow more complex assignments of the relations. It would also be nice to have access to $current in the processor without extracting it from name parameter. This would allow things like:

items:
  a1:
    order: '0'
    parent: '@p1'
  a2:
    order: '1'
    parent: '@p1'
  a3:
    order: '2'
    parent: '@p1'
  a4:
    order: '3'
    parent: '@p1'
  a5:
    order: '4'
    parent: '@p1'
  a6:
    order: '0'
    parent: '@p2'

to be replaced by

processor:
object.order = current % 5;
object.parent = `@p${current%5}`;


items:
  a{1..1}:

npx fixtures ./fixtures --config ormconfig.js --connection Diligence

UnhandledPromiseRejectionWarning: ConnectionNotFoundError: Connection "default" was not found.

npx fixtures ./fixtures --config ormconfig.js -cn Diligence

TypeOrm config /Users/samcong/code/repo/n not found

Config

module.exports = [
{
name: "Diligence",
type: "mssql",
host: "localhost",
port: 11433,
database: "Diligence",
username: "sa",
password: "password",
entities: ["src/models/**/*.ts"]
}
];

Hi,

There are many examples where related object is fully inserted into the parent object but, sometimes, you need just one field from the related object (e.g. id). Is it possible to do something like:

profileId: `@profile5.id`

I know I can do it using processors but it looks a bit ugly, imo.

Thank you.

I have a subscriber class and I want it to execute the method afterInsert after the corresponding fixture has been inserted into the database. Is it possible to do this?

Thanks in advance.

Probably more of a question than a bug, but I guess we'll see...

I am trying to create fixtures for a table that has several ManyToOne relations.

UserGroup.ts

@Entity()
export default class UserGroup {
  @PrimaryGeneratedColumn()
  public id!: number;

  @ManyToOne(
    () => User,
    user => user.userGroups,
    { primary: true }
  ) // inverse "userGroups: UserGroup[]" is one-to-many in user
  @JoinColumn({ name: 'user_id' })
  user!: User;

  @ManyToOne(
    () => Group,
    group => group.userGroups,
    { primary: true }
  ) // inverse "userGroups: UserGroup[]" is one-to-many in group
  @JoinColumn({ name: 'group_id' })
  group!: Group;

  @Column({ name: 'status' })
  status: UserGroupStatus = UserGroupStatus.ACTIVE;
}

User.ts

@Entity()
export default class User {
...
  @OneToMany(
    _type => UserGroup,
    userGroup => userGroup.user,
    {
      eager: true
    }
  )
  userGroups!: UserGroup[];
}

and then the same for Group.

I am trying to populate the fixtures with:

User.yml

entity: User
items:
  user{1..2000}:
   ...
   userGroups: ["@userGroups*"]

entity: Group
items:
  group{1..2000}:
   ...
   userGroups: ["@userGroups*"]

UserGroup.yml

entity: UserGroup
items:
  userGroups{1..2000}:
    user_id: "@user($current)"
    group_id: "@group($current)"
    status: "{{random.number(4)}}"

But when I run the cli, I get the following error:

Fail fixture loading: Maximum call stack size exceeded
RangeError: Maximum call stack size exceeded
    at Resolver.resolveDeepDependencies (/usr/app/server/node_modules/typeorm-fixtures-cli/dist/Resolver.js:118:31)
  ...

What am I doing wrong? I assume this is because of a circular reference between UserGroups and the User/Group entities, but I don't see how else I can create a relationship between the entities.

• $ref support (fixture scope)
• config support
• configure faker locale (implemented in 1.8.0)
• optional data
• reference to property
• extend fixtures file
• logger / debug
• integration tests
• class-transformer support
• require option for registred ts-node and other
• support tree repository
• optional ignoreDecorators [true/false] #87

I have a manyToMany relationship in one of my entities and if I comment it out it works fine: something like the following:

@ManyToMany(type => Subject, subject => subject.tutors)
@JoinTable()
subjects: Subject[]

after trying to run the fixture I get:

Fail fixture loading: Maximum call stack size exceeded
RangeError: Maximum call stack size exceeded

Has anyone tried getting fixtures to work with ManyToMany relationships?

Is it possible to use a random string from predefined values? It would be useful for enum fields, for example

Hi,

I've created a fork to work on the ability to resolve promises for lazy loaded relations in typeorm. The idea is to have the same principle as resolving references but adding a promise.resolve once it has been resolved.

https://github.com/getbigger-io/typeorm-fixtures/blob/master/src/parsers/PromiseReferenceParser.ts

I am facing issues in the Builder expecially regarding the usage of the class-transformer package. The current code is the following:

plainToClassFromExist(entity, data, { ignoreDecorators: true }) -> decorator are ignored and the class-transformer produces the following plaintToClass transformation:

MyEntity {
  id: 'c0ed46a6-7c84-4879-9bbb-4123897eb122',
  name: 'DEMO',
  __promise_property__: Promise { <pending> }
}

I fully understand why the option is there, but I cannot find any solution to get rid of this and get the resolved promise in the transformation output.

If you have any idea on how we can easilly solve this step and get the proper property names in the output it would be great !
Thanks

we use ormconfig.ts because it is most flexible for configuration TypeOrm
npx fixtures -c ormconfig.ts database/fixtures
output

Fail fixture loading: Unexpected token {
(node:32337) UnhandledPromiseRejectionWarning: ConnectionNotFoundError: Connection "default" was not found.

Seems that I can't use such definition:

entity: Ring
items:
  ring{0..10}:
    date: '{{date.past(5, '2018-01-01')}}'

because this method gets only one param which is:
5, '2018-01-01' concatenated string

I need an option to add relations in preProcessor dynamcily is this possible?

I'm using a table with an enum type field. For example "text" and "image".
Depending on the type I will add a relation for image or text and now I want to create fixtures for this.
Do you have an idea how I can handle this?

Hello,

Thank you for this nice and handy library!

I have entity with decorators (I use DateTime type from luxon) and had problem because attribute of type DateTime cannot be created with new DateTime(). In luxon, you have to use DateTime.local() or DateTime.utc() to create new instances.

So I have write some decorators to get around this. However, my decorators are ignored when fixtures are transformed due to the parameter ignoreDecorators set to true in the call to plainToClassFromExist in Builder.js

if (typeof processorInstance.preProcess === 'function') {
                    data = yield processorInstance.preProcess(fixture.name, data);
                }
                entity = class_transformer_1.plainToClassFromExist(entity, data, { ignoreDecorators: false });
                yield callExecutors();
                /* istanbul ignore else */
                if (typeof processorInstance.postProcess === 'function') {
                    yield processorInstance.postProcess(fixture.name, entity);
                }

What are the reasons for setting ignoreDecorators to true? Could you make it optional?

• __calls
• <(current())>
• <{parameters}>
• ejs
• Faker.js
• Documentation
• unit tests

The devDependency @types/chai-as-promised was updated from 7.1.1 to 7.1.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/chai-as-promised is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Context:
I have a relation like so:

Sport.ts

import { Field, ObjectType } from 'type-graphql';
import { Column, Entity, OneToMany, Unique } from 'typeorm';

import { TimeFrame } from '..';
import Base from '../Base';

@ObjectType()
@Entity({ name: 'sports' })
export default class Sport extends Base {
  @Column({ type: 'text' })
  label: string;

  @Field(() => [TimeFrame])
  @OneToMany(() => TimeFrame, (timeFrame) => timeFrame.sport, { lazy: true })
  timeFrames: TimeFrame[];
}

TimeFrame.ts

import { Field, ObjectType } from 'type-graphql';
import { Column, Entity, JoinTable, ManyToMany, ManyToOne, OneToMany } from 'typeorm';

import { Sport } from '..';
import Base from '../Base';

@ObjectType()
@Entity({ name: 'time_frames' })
export default class TimeFrame extends Base {
  @Column({ type: 'text' })
  label: string;

  @Field(() => Sport)
  @ManyToOne(() => Sport, (sport) => sport.timeFrames, { lazy: true })
  sport: Sport;
  @Column({ nullable: false })
  sportId: string;
}

In my timeFrame fixture, I need to access sportId and not just sport. To solve, I want to implement a preprocessor to set the ID based on the sport relation.
With programmatic setup, if I add a preprocessor it just hangs while building the entity.

loadFixtures.ts

import * as path from 'path';

import { Connection, getRepository } from 'typeorm';
import {
  Builder,
  IEntity,
  Loader,
  Parser,
  Resolver,
} from 'typeorm-fixtures-cli/dist';

import testConnection from '../../testUtils/testConnection';

import { asyncForEach } from './../../utils/helpers';

interface ICreatedFixtures {
  [entity: string]: IEntity;
}
interface IFixtures {
  conn: Connection;
  createdFixtures: ICreatedFixtures;
}

const loadFixtures = async(fixtureFiles: string[]): Promise<IFixtures> => {
  const conn = await testConnection();
  const loader = new Loader();
  fixtureFiles.forEach((file) => {
    loader.load(path.resolve(`src/__spec__/fixtures/${file}.yml`));
  });

  const resolver = new Resolver();
  const fixtures = resolver.resolve(loader.fixtureConfigs);
  const builder = new Builder(conn, new Parser());

  const createdFixtures: ICreatedFixtures = {};
  await asyncForEach(fixtures, async(fixture) => {
    console.log('before build', fixture);

    const entity = await builder.build(fixture);
    console.log('after build');
    const { tableName } = conn.manager.getRepository(fixture.entity).metadata;

    await conn.manager.query(`DELETE FROM ${tableName}`);

    createdFixtures[fixture.name] = await getRepository(entity.constructor.name).save(entity);
  });

  return { conn, createdFixtures };
};

export default loadFixtures;

timeFrames.yml

entity: TimeFrame
processor: ../processors/TimeFrameProcessor
items:
  timeFrame:
    label: Game
    sport: '@sport'
    idx: 0

TimeFrameProcessor.ts

import { IProcessor } from 'typeorm-fixtures-cli/dist';

import { TimeFrame } from '../../db/entity';

export default class TimeFrameProcessor implements IProcessor<TimeFrame> {
  preProcess(name: string, object: TimeFrame): any {
    return object;
  }
}

It's logging before build but not after build. If I remove the preProcess method it resolves it.
Thanks!

Your Environment

I was wondering if it's possible to use the current iteration as a string value in a field instead of just referencing relations. Like this:

entity: User
items:
  user{1..10}:
    firstName: '{{name.firstName}}'
    lastName: '{{name.lastName}}'
    email: 'email{{current}}@gmail.com'

This way all the fixtures will have [email protected] -> [email protected]

Your Environment

Hello!

I'm facing with a strange behavior using typeorm-fixtures with a NestJS application. When I try to run the fixtures, I'm getting this error:

Fail fixture loading: No repository for "Object" was found. Looks like this entity is not registered in current "default" connection?

After some investigation, I noticed that the error occurs in the line 112 of cli.ts file.

await connection.getRepository(entity.constructor.name).save(entity);

The problem seems to be that getRepository function is using the entity.constructor.name to get the repository for the entity. But at runtime, the constructor.name is equal to Object (I am right?). I think changing the line to:

await connection.getRepository(fixture.entity).save(entity)

At least I tested it locally and it worked

I'm getting the related error using this comand:

node_modules/.bin/fixtures ./test/fixtures --config ./ormconfig-e2e.ts --sync --require=ts-node/register --require=tsconfig-paths/register

I'd like my fixtures to be generated randomly, but with a seed.
For faker fields, I use faker.seed(777).
However, this doesn't work with "*" relations.
I tried to use seedrandom package and replace global random, but it doesn't work with global lodash instance which this package uses in ReferenceParser. So I hardcoded seedrandom like this: https://github.com/doomsower/typeorm-fixtures/blob/70cdea8d407fa8d9b9b0f3f29e5a12231ffa875c/src/parsers/ReferenceParser.ts#L14

I think this is a nice feature, but currently there's no mechanism to pass params to parsers, as everything is hardcoded.

I tried to create several datasets for testing our application.
Starting with 100 base objects * 4 sub objects + a few thousand additional entities. Takes ~1 min
1000 * 4 + x thousand. Takes ~4min
10000 * 4 + x thousand. Crashes after 4+ hours.

Debug output

Connection to database...
Database is connected
Loading fixtureConfigs
Resolving fixtureConfigs

Node Profiling of first 5minutes.

Looks like most time is spend in the resolver at resolveDeepDependencies(item) {

Hi,

I've got an application where database schema is designed to store immutable data and every new row represents new revision of the data. Thus the order of rows is very important.

I noticed after using this package that because of dependency resolving some of the entities I created were not being saved to database in the same order specified in the .yml file.

I thought that one way could be adding an option in where previous node would be set to dependency.

More flexible implementation of this would be to allow Fixture item tell that it depends on previous item in Fixture.yml

I have some entities being inserted via triggers in DB, and having a unique index (independent of the PK). Using fixtures, it's not possible to know what the row id will be in before, but I would like to use it later on to append relations on those entities.

So far I have tried creating a load processor to read the id and perform the update there, using the unique index columns. The update is done, but, I get a weird error afterwards:

Fail fixture loading: Could not find any entity of type "ProjectMap" matching: {
    "where": {}
}

My preProcess function:

  async preProcess(name: string, obj: ProjectMap): Promise<ProjectMap> {
    const repository = getConnection().getRepository(ProjectMap);
    const { id } = await repository.findOneOrFail({ select: ['id'], where: { method: obj.method, resourceId: obj.resource.id } });
    obj.id = id;

    await repository.save(obj);

    return derived;
  }

I cannot find how the save fails afterwards, however perhaps I could skip the library's save by returning null?

The devDependency tslint-immutable was updated from 5.3.3 to 5.4.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

tslint-immutable is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Hi everyone,

First of all, thanks for this awesome library, it's so useful!

I would like that typeorm-fixtures provide some way to change the Fakerjs locale. That's all.

Thanks in advance.

when I set data for Users entity I got extra fields in DB
My Users entity:

import { Column, Entity, PrimaryGeneratedColumn } from "typeorm";

@Entity()
export class Users {
  @PrimaryGeneratedColumn()
  id: number;

  @Column({ length: 100 })
  name: string;
}

I got:

With other entities all good, but not with this. What can it be?

Your Environment

| Software | Version(s) |
| typeorm-fixtures-cli | 1.8.0 |
| Node | 14.5.0
| Yarn | 1.22.4
| Operating System | MacOs 10.15.7

I have the following relation:

• A Team entity
• A Source entity
• A News entity, that has ManyToOne relationship with Team and Source

@ManyToOne(() => Source)
@JoinColumn({ name: "sourceId" })
source: Source;

@ManyToOne(() => Team)
@JoinColumn({ name: "teamId" })
team: Team;

• A Comment entity, that has ManyToOne relationship with a News and a Comment

@ManyToOne(() => News)
@JoinColumn({ name: "newsId" })
news: News;

@ManyToOne(() => Comment)
@JoinColumn({ name: "parentId" })
parent: Comment | null;

I'm trying load some comments in database but, if all News have a Team then I get this error:

If I leave some News without a Team then the fixtures are loaded. But the Comments are related just with the News without a Team.

Using a console.log I found that the parse method in ReferenceParser is been called with the entities without any news. So, probably the library is trying load the comments when there is no news created.

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The devDependency conventional-changelog-cli was updated from 2.0.33 to 2.0.34.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

conventional-changelog-cli is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

"typeorm-fixtures-cli": "^1.3.5"

Getting error when run fixtures Ads.yml:

Fail fixture loading: Entity metadata for Category#ads was not found.

maybe is bug?

@Entity('ad')
export class Ad {
  @PrimaryGeneratedColumn
  id: number;
  @Column()
  title: string;
  @ManyToMany(type => Category, category => category.ads)
  @JoinTable({ name: 'ad_category' })
  categories: Category[];
}

@Entity('category')
export class Category {
  @PrimaryGeneratedColumn()
  id: number;
  @Column)
  name: string;
  @ManyToMany(type => Ad, ad => ad.categories)
  ads: Ad[];
}

Ads.yml

entity: Ad
items:
  ad{1..100}:
    title: '{{name.jobType}}'
    categories:
      category1:
        name: '{{name.jobArea}}'

🚨 Reminder! Less than one month left to migrate your repositories over to Snyk before Greenkeeper says goodbye on June 3rd! 💜 🚚💨 💚

Find out how to migrate to Snyk at greenkeeper.io

The devDependency typeorm was updated from 0.2.24 to 0.2.25.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

typeorm is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

I've been trying to check the possibility to set the generation seed for the fixtures, so they can be reproducible in tests, however I haven't seen the faker.seed() call anywhere in the code.

Is there any possibility to add some sort of configuration to the project so tests can be reproducible?
This way, fixtures can be loaded before tests and tests can be reproducible.

Otherwise, each time fixtures are run, the values in the database get updated

Due to https://github.com/RobinCK/typeorm-fixtures/blob/master/src/parsers/FakerParser.ts#L15 it's impossible to have a string with literal double curly, for example:

entity: User
items:
  user0:
    comment: 'here is a liquid template {{ my_variable }}'

will fail to build with a Invalid module: my_variable exception thrown by faker.

I think we need a different validation of the entity which does not require alphanumeric. I don't think its the responsibility of this library to ensure the naming validations of a database driver.

I have a category entity set up like in the example that optionally points to another category, creating a parent/child relationship. The topmost categories don't have a parent (so its parent attribute is nullable)

My fixture looks like this:

entity: Category
items:
  category1:
    name: 'first'
    parent: null
    sortId: 1

I get an error when it tries to insert the fixture, because it tries to insert a second, empty category.

I've traced through the code to see what it's doing and it converts the {parent:null} from the fixture to an empty object {parent: {}} in the Entity.

How can I reference the title of the current iteration to slugify it with faker.helpers.slugify. I would expect something like so

entity: Post
items:
  post{1..10}:
    title: '{{lorem.words}}'
    slug: '{{helpers.slugify(@title)}}'
    body: '{{lorem.paragraphs}}'

Hey. Thank you for this great project!

My main intention with this lib is to load fixtures for automated testing on a Nest project.
But after reading the following statement in the README, it has brought me doubts about the purpose of this library:

Although typeorm-fixtures-cli is intended to use as a CLI, you can still load fixtures via APIs in your program.

Loading the fixtures using the CLI means the data will be loaded once for the entire testing suite.
One general practice for automated testing is to isolate testing data between testing cases.
I'm trying to figure out why programmatically loading is not faced as the first option here. 🙃

Calling Methods feature only works when a processor is defined

https://github.com/RobinCK/typeorm-fixtures/blob/master/src/Builder.ts#L57