Prisma1: Internal Server Error when Adding Type Called User that has extra fields

Created on 8 Sep 2017  路  5Comments  路  Source: prisma/prisma1

Issue by do4gr
_Friday Aug 25, 2017 at 14:27 GMT_
_Originally opened as https://github.com/graphcool/api-bugs/issues/241_


This is a bug.

What is the current behavior?

When creating a fresh project and trying to add a copy of the User type there is a warning.

type User implements Node {
  createdAt: DateTime!
  id: ID! @isUnique
  updatedAt: DateTime!
}

If instead, you add the exact same type, but add an extra field, an internal server error is returned.

type User implements Node {
  createdAt: DateTime!
  id: ID! @isUnique
  updatedAt: DateTime!
  anotherField: String
}

The error for duplicate type name should be returned in both cases..

bu2-confirmed

All 5 comments

Is that still the case in the latest CLI version, @do4gr?

yes. Still results in an internal server error.

Will be cleaned up when #454 is tackled I guess.

Now that #454 is closed, can you look into this again, @do4gr? I assume this is fixed now.

Still occuring. Not confined to user or system types. Will happen on any type. I will fix it.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

dohomi picture dohomi  路  3Comments

schickling picture schickling  路  3Comments

tbrannam picture tbrannam  路  3Comments

MitkoTschimev picture MitkoTschimev  路  3Comments

marktani picture marktani  路  3Comments