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

Fix to exhaustively satisfy for node lists #391

Merged
merged 2 commits into from
Sep 22, 2021

Conversation

sunesimonsen
Copy link
Member

@sunesimonsen sunesimonsen commented Sep 22, 2021

We forgot to pass on the exhaustively flag.

@sunesimonsen sunesimonsen force-pushed the ssimonsen/satisfy-exhaustively branch from f1ce142 to b19467a Compare September 22, 2021 20:59
@coveralls
Copy link

coveralls commented Sep 22, 2021

Pull Request Test Coverage Report for Build 1263474805

  • 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 92.709%

Totals Coverage Status
Change from base Build 1224533132: 0.0%
Covered Lines: 704
Relevant Lines: 740

💛 - Coveralls

@sunesimonsen
Copy link
Member Author

I'll merge as this is a non-controversial bugfix and we have lots of tests to prove things still work.

@sunesimonsen sunesimonsen merged commit d5c2983 into master Sep 22, 2021
@sunesimonsen sunesimonsen deleted the ssimonsen/satisfy-exhaustively branch September 22, 2021 21:13
@papandreou
Copy link
Member

Whoops, nice catch! 💪

@alexjeffburke
Copy link
Member

@sunesimonsen I read it over briefly yesterday and it made good sense 👌

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

Successfully merging this pull request may close these issues.

4 participants