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

schema: fix error message when provided type has no name #2475

Merged
merged 2 commits into from Mar 6, 2020

Conversation

Cito
Copy link
Member

@Cito Cito commented Mar 4, 2020

Small fix to show an error message when one provided type has no name and to avoid error messages like "multiple types named undefined" when multiple provided types have no name.

Avoid confusing error message about "multiple types named undefined".
throw new Error(
'One of the provided types for building the Schema is missing a name.',
);
}
Copy link
Member

Choose a reason for hiding this comment

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

Since according to TS & Flow typings namedType always have name it should be devCheck.

Copy link
Member Author

Choose a reason for hiding this comment

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

Ok, changed that.

@IvanGoncharov IvanGoncharov merged commit 63c2009 into graphql:master Mar 6, 2020
@Cito Cito deleted the schema-types-without-names branch March 6, 2020 15:21
@IvanGoncharov IvanGoncharov added the PR: bug fix 🐞 requires increase of "patch" version number label Apr 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PR: bug fix 🐞 requires increase of "patch" version number
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants