Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot control nullability of projected values #1005

Open
edjiang opened this issue Dec 21, 2020 · 0 comments
Open

Cannot control nullability of projected values #1005

edjiang opened this issue Dec 21, 2020 · 0 comments

Comments

@edjiang
Copy link

edjiang commented Dec 21, 2020

Not sure if this is a feature or bug? 🙃

model User {
  phoneNumber    String          @unique
  emailAddress   String?         @unique
}
objectType({
    name: 'User',
    definition(t) {
        t.model.phoneNumber()
        t.model.emailAddress()
    }
})

will render to:

type User {
  phoneNumber: String!
  emailAddress: String
}

Note that phoneNumber, despite being nullable in the Nexus definition, will render required in the graphql definition. Adding .nullable does not change anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant