Make single error instance of Error to prevent [object Object] error messages

[ghost]

A fix for #1046

TODO:

• If this PR is a new feature, reference an issue where a consensus about the design was reached (not necessary for small changes)
• Make sure all of the significant new logic is covered by tests
• Rebase your changes on master so that they can be merged easily
• Make sure all tests and linter rules pass
• Update CHANGELOG.md with your change. Include a description of your change, link to PR (always) and issue (if applicable). Add your CHANGELOG entry under vNEXT. Do not create a new version number for your change yourself.

[apollo-cla]

@almostprogrammer: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/

[hwillson]

Thanks for working on this @almostprogrammer. Are you able to look at the test failures? They seem relevant.

[ghost]

@hwillson a test that fails is not related to my fix. In fact it also fails in master

[shawnXiao]

I also have the same test failure.
Maybe the test case have some problem.
I search the GraphQL specification, there is no refer about the fragment with parameter.
I also have a look about GraphQL-JS source code, the problem which occur at validate the schema definition at the KnownTypeNames.js.
@hwillson

[kommander]

@almostprogrammer Awesome, I hope this gets through soon. I fixed this in graphqljs, but have to wait for 14.2 release https://github.com/graphql/graphql-js/pull/1600/files#diff-7216927a33b2b307f325a8190e6fbf9bR746

[fenos]

Hi there,
Any progress on merging this? It's a vital fix that we are all waiting for 😄

[MrLoh]

Would be great to see this merged

[fenos]

mergy mergy 😄🙏

[MrLoh]

Could this be merged, it's really annoying to depend on patch-package for such a stupid issue that already has a PR since 3 months.

[yaacovCR]

This should be fixed in graphql-tools-fork.

[yaacovCR]

Closing in favor of #1307