-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Provide people with tabs so they can use classes as well #4284
Conversation
Hi @JoviDeCroock, I'm @github-actions bot happy to help you with this PR 👋 Supported commandsPlease post this commands in separate comments and only one per comment:
|
bc93642
to
a3e172a
Compare
a3e172a
to
ff51604
Compare
076abdb
to
53dae86
Compare
53dae86
to
a0cd603
Compare
a0cd603
to
b036677
Compare
b036677
to
b6a6028
Compare
b6a6028
to
401dcac
Compare
401dcac
to
7a5f066
Compare
7a5f066
to
9b84ceb
Compare
9b84ceb
to
4af2c5d
Compare
39ac537
to
4386ab0
Compare
4386ab0
to
7aef054
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven’t found the time yet to get through every line, but I love the idea of tabs!
One question I have is whether we want to call these SDL-first vs code-first …. Our SDL-first currently requires using the root value/parent method of providing resolvers but the eventual plan would be to allow resolvers as additional arguments to buildschema just like graphql tools makeExecutableSchema…
7aef054
to
7a298ee
Compare
This provides people with the option to choose between the template approach or the classes approach. This is a proposal to tackle #1368
Preview
This has been applied throughout the codebase now, however one of the things I am uncertain about is how we offer
buildSchema
with the GraphQLDefer/... directives? Should we add an option tobuildSchema
? The exports defined in that chapter seem to only exist in v17 so we should explicitly flag that.