-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Use SBT doctest plugin #724
Conversation
This helps ensure that our ScalaDoc examples actually compile and produce the expected result.
Resolves #487. I think the only example I haven't converted is one in |
@ceedubs Are we still considering collapsing |
@mpilquist I haven't heard that come up recently. It does seem a little odd to me that |
The builds failed. My guess is that it's because doctest brought in its own version of Scalacheck and I need to be explicit about using our version. I'll look into it. |
Since we are explicitly using ScalaCheck it is a good idea to not let sbt-doctest add ScalaCheck as a dependency with |
This was causing some build failures. Also use an explicit dependency on our version of scalacheck instead of letting sbt-doctest bring in its own version.
The build has been hanging during tests in the `free` module recently, and I suspect this may be the cause.
Current coverage is
|
I don't see any doctest output in the build log. I think we need to add |
This is awesome! |
The sbt-doctest plugin generates tests within the `core` module.
Wow, good eye, @fthomas. It should be fixed now. |
This looks great. Makes me think how nice things would be if Travis were able to publish doc ... somewhere ... so reading doc in its final form could be part of the PR review process. |
Okay I think this is good now. I see the following in the Travis build output:
|
👍 Great work, @ceedubs! I particular like that this shows which imports are necessary to bring the various instances into scope. Leaving out imports in examples can be frustrating for beginners and annoying for experts. |
It sounds like there is general approval, so I'm going to go ahead and merge (in part because I'm hoping the changes to the |
This helps ensure that our ScalaDoc examples actually compile and
produce the expected result.