Skip to content

Make "nonnull-test.js" more explicit#1311

Merged
leebyron merged 5 commits intographql:masterfrom
IvanGoncharov:nonullTests
Apr 18, 2018
Merged

Make "nonnull-test.js" more explicit#1311
leebyron merged 5 commits intographql:masterfrom
IvanGoncharov:nonullTests

Conversation

@IvanGoncharov
Copy link
Copy Markdown
Member

It was really hard to read those tests.
Moreover, explicit version is shorter and this PR increase line count only because I added path to every error.

@leebyron
Copy link
Copy Markdown
Contributor

Looks like this has merge conflicts and test failures - want to take another look, @IvanGoncharov ?

@IvanGoncharov
Copy link
Copy Markdown
Member Author

@leebyron Rebased and fixed. The reason was that #1286 changed the order of errors in a promise-heavy test. Not a problem since the order of error is implementation dependent. Maybe it worth to sort them, somehow?

It went unnoticed on master since containSubset doesn't check the order of elements in arrays.

@leebyron
Copy link
Copy Markdown
Contributor

Aha, I'm glad we're migrating away from containSubset - the array order thing is not what I would have suspected

@leebyron leebyron merged commit 32e2f33 into graphql:master Apr 18, 2018
@leebyron
Copy link
Copy Markdown
Contributor

Thanks for cleaning this up! It's much easier to follow now and I'm happy to see path included in the test expectations

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