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

Remove usage of Flow placeholder argument + cleanup #1669

Merged
merged 1 commit into from
Jan 16, 2019

Conversation

IvanGoncharov
Copy link
Member

No description provided.

deprecationReason: getDeprecationReason(field),
astNode: field,
};
}

buildInputField(value: InputValueDefinitionNode): GraphQLInputField {
buildArg(value: InputValueDefinitionNode): GraphQLArgumentConfig {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We probably shouldn't expose this, as we're not building a schema GraphQLArgument but just a GraphQLArgumentConfig.

Having buildFoo sometimes return a GraphQLFoo and sometimes a GraphQLFooConfig is confusing.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh I see we're already doing this with buildField. That is quite confusing but is fine then. I wish buildDirective was also building a GraphQLDirectiveConfig too, but that ship has sailed. Maybe a wishlist for v15?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mjmahone The entire class is internal it's just a bunch of functions that buildSchema/extendSchema are using.
So it's just cleanup of internal API.

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

Successfully merging this pull request may close these issues.

3 participants