Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Okay, trying this again, with 1.0.0-RC4.
Update: the NPEs were because of an initialization issue in
cats.kernel.laws.Test
, which was happening because the implicitPropertyCheckConfiguration
is now being resolved wherecheckAll
is called instead of in discipline-scalatest (where previously it always usedgeneratorDrivenConfig
).Unfortunately ScalaTest's
org.scalatest.prop.Configuration
definesgeneratorDrivenConfig
as aval
, so we can't just slap alazy
on the override. Instead I've added a configuration class that makes the initialization work out right.This is the only place this issue showed up either here or in Circe, which I've also updated to discipline-scalatest 1.0.0-RC4, and I think it's likely to be rare—it's only showing up here because of the kind of unusual arrangement of Scala-version-specific tests.
I also think the new behavior is the correct behavior. If the user was writing tests in terms of
check
directly, the implicit configuration would be resolved at the point where they callcheck
—it wouldn't just usegeneratorDrivenConfig
automatically. In my view ourcheckAll
should do the same.(I'll note the issue in the final 1.0.0 release notes.)