Open nettrino opened 1 year ago
Classes like UserAccount which inherit from other classes don't re-define their fields (e.g., name is not part of the UserAccount class in the generation bits as it is part of the Account class assuming the following spec:
UserAccount
name
Account
interface Account { name: String! } """ An individual user account """ type UserAccount implements Account { email: Email! @unique name: String! avatarURL: String type: NodeType! @default(value: USER_ACCOUNT) definedIn: ResourceEntity @relationship(type: "HAS_ACCOUNT", direction: IN) }
However, the fields should be emitted for the CreateInput versions of the classes to be used in mutations
CreateInput
This is related to directives being improperly parsed.
Classes like
UserAccount
which inherit from other classes don't re-define their fields (e.g.,name
is not part of theUserAccount
class in the generation bits as it is part of theAccount
class assuming the following spec:However, the fields should be emitted for the
CreateInput
versions of the classes to be used in mutations