[Bug] Postgres 'timestamptz' column failing at parsing long date about typeorm-fixtures

[CiotkaCierpienia]

Hi,
I have the same problem, I would love to see just ISO date returned by date.past and date.future, as faker-js returns exactly that, forcing us to use Date().toISOString defeats all purposes of using faker here...

(thanks @lordrip for the workaround)

[lordrip]

I've forgot to mention, if I can help somehow investigating this further, just let me know :)

[lordrip]

As a workaround, I'm using ejs forcing an ISO string

entity: MyEntity
items:
  sync{1..3}:
    topic: 'a-given-topic'
    id: '{{datatype.uuid}}'
    company: '@company*'
    syncDateTime: <%= (new Date()).toISOString() %>

[lordrip]

Another way to approach this in the meantime could be leveraging Processors.

import { IProcessor } from 'typeorm-fixtures-cli';
//  Importing 'YourEntityEntity' it's optional, it's mostly for typing purposes
import { YourEntity } from './yourentity';
import { faker } from '@faker-js/faker';

export default class EntityProcessor implements IProcessor<YourEntity> {
  async preProcess(name: string, entity: YourEntity): Promise<YourEntity> {

    // Here we can leverage any fakerjs module
    // We could also leverage location.zipCode but for the sake of the example, we send some parameters as well
    const zipCode = faker.string.numeric({ length: 5, allowLeadingZeros: true });

    return { ...entity, zipCode };
  }
}

then in the fixture yaml file

entity: YourEntity
processor: ./EntityProcessor # Load the above processor
items:
  provider{1..10}:
    id: '{{string.uuid}}'
    # zipCode is no longer required here as we're providing it through the processor
    name: '{{company.name}}'
    address: '{{location.streetAddress}}'
    phone: '{{phone.number}}'
    email: '{{internet.email}}'
    representativeName: '{{person.fullName}}'
    representativePhone: '{{phone.number}}'
    representativeEmail: '{{internet.email}}'