You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
}
The text was updated successfully, but these errors were encountered:
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:
Example extension file content :
The text was updated successfully, but these errors were encountered: