Not working on unsupported types (sqlite)

[jsbrain]

In case of sqlite the generator won't create faker objects despite the annotations because it's listed as string.
But there are extensions for sqlite that would allow this also there could be manual serialization.

Would be great if that's supported.

model users {
  id    String @id @default(cuid())
  email String @unique
  name  String

  ///FAKE:fakeSettings()
  settings String? @default("{}") /// <- This doesn't work

  ///FAKE:{notificationsEnabled: faker.datatype.boolean(), preferredColor: faker.color.rgb()}
  ui_settings Unsupported("json") /// <- This doesn't work either

  profile profiles?
}

[luisrudge]

Interesting. Thanks for the issue. Not sure what Prisma will report in the DMMF.Field object for fields like this. Can you write a failing test for it?

• Create a new sqlite.prisma file in src/__tests__
• Create a new method to retrieve the sqlite DMMF
• Create a new test in createMethods.test.ts that uses the sqlite DMMF to do any assertions. Feel free to add only your specific use case instead of adding all other types

If you find a fix for it, even better 😅 Otherwise I'll investigate with the help of the failing test.

[jsbrain]

I'm very limited on time right now but I think changing this:

if (['String'].includes(field.type)) {
  return `${field.name}: '${field.default}'`;
}

to this:

if (['String'].includes(field.type)) {
  const docLines = field.documentation?.split('\n') || [];
  const fake = docLines.find((line) => line.startsWith('FAKE:'));
  if (fake) {
    const fakeValue = fake.replace('FAKE:', '');
    if (!fakeValue) {
      logger.warn(
        `Incorrect format for fake JSON. Field ${field.name} won't be generated. Example: ///[FAKE:{"test": "faker.lorem.word()"}]`,
      );
      return null;
    }
    return `${field.name}: ${fakeValue}`;
  }
  return `${field.name}: '${field.default}'`;
}

should do it.

[jsbrain]

Basically keeps the current implementation unless there is a FAKE: comment. Should be fine I guess?