Skip to content

Allow to override existing schema with GraphQL-faker  #156

Open
@rossoha

Description

@rossoha

At the moment faker doesn't allow to override fields that already on the backend, but there might be a situation when existing API is not yet implemented and return some default value (like null). So it would be nice to have a way to override such a response.

Example error message: Field "User.firstName" already exists in the schema. It cannot also be defined in this type extension.

Example schema from server:

type User {
    _instanceName: String
     id: UUID
    firstName: String
    lastName: String
}

Example extension file content :

extend type User {  
  firstName: String @fake(type: firstName)
}

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions