schema validation errors should not trigger an error reporting

[Jolg42]

Bug description

This triggers the reporting error but it should not.

How to reproduce

• Run npx @prisma/cli@dev migrate save --name init --experimental

Expected behavior

A Schema parsing / validation error (with a code) that doesn't trigger an error report.

Prisma information

datasource my_db {
  provider = "sqlite"
  url      = "file:dev7.db"
}

model Blog {
  id          Int @id
  viewCount20 Intss
}

@tomhoule I guess this could be fixed if the error(s) have an error code.

[tomhoule]

I think they already do (it should be a known error with an error code already). I can double check after my vacation.

[Jolg42]

Indeed I will fix that in client then!

  MigrateEngine:rpc {
  MigrateEngine:rpc   jsonrpc: '2.0',
  MigrateEngine:rpc   error: {
  MigrateEngine:rpc     code: 4466,
  MigrateEngine:rpc     message: 'An error happened. Check the data field for details.',
  MigrateEngine:rpc     data: {
  MigrateEngine:rpc       is_panic: false,
  MigrateEngine:rpc       message: 'error: Type "Intss" is neither a built-in type, nor refers to another model, custom type, or enum.\n' +
  MigrateEngine:rpc         '  -->  schema.prisma:8\n' +
  MigrateEngine:rpc         '   | \n' +
  MigrateEngine:rpc         ' 7 |   id          Int @id\n' +
  MigrateEngine:rpc         ' 8 |   viewCount20 Intss\n' +
  MigrateEngine:rpc         '   | \n',
  MigrateEngine:rpc       meta: [Object],
  MigrateEngine:rpc       error_code: 'P1012'
  MigrateEngine:rpc     }
  MigrateEngine:rpc   },
  MigrateEngine:rpc   id: 2
  MigrateEngine:rpc } +20ms