discipline-core-1.0.0 and discipline-scalatest-1.0.0-M1 are here, discipline-specs2-1.0.0 is coming soon: tweet
but on the latest release it requires me to include a
checkAll method
Thus I can’t use it for cases besides law checking
Why was it changed?
Are you using the scalatest integration?
There are a few implementations in the same package as
Discipline, if you've picked a scalatest style, that define checkAll. You might want one of those.
CatsSuite extended
Discipline but now it extends FunSuiteDiscipline
In case anyone's interested, I made https://github.com/rpiaggio/discipline-munit. It's quite trivial given MUnit's integration with Scalacheck, but it bridges the gap. Current version is
0.1.0. Please let me know if you want me to add a PR mentioning it in discipline's README.
Then it'd be consistent in package and location. Might help people find it, and of course we could leave you as an admin on it.
When you transfer a repository that you own to another user account, the new owner will receive a confirmation email. The confirmation email includes instructions for accepting the transfer. If the new owner doesn't accept the transfer within one day, the invitation will expire.
The original owner of the repository is added as a collaborator on the transferred repository. Other collaborators to the transferred repository remain intact.
That looks like exactly what we want. Gets the project alongside its siblings, and keeps you in charge of it.
The maintenance on the others has mostly been merging scala-steward PRs. :laughing:
OK, I'll do the transfer, thank you! but before that, I have the dual question as before since I'll probably implement the suggestion from https://gitter.im/scalameta/munit?at=5eb3d132d6b5a360e43c339a. So, is it OK to move the project into Typelevel if the package name is not
org.typelevel.discipline.munit anymore, but just munit ?
I am an old Java programmer, and I like the reverse domain name convention, and I like it when the organization ID matches the package name. But these opinions all make me old-fashioned.
There are other Typelevel projects that have a bare root name.
jawn comes to mind.
You don’t have the permission to create public repositories on typelevel
Oh, I see the fine print now.
To transfer a repository that you own to an organization, you must have permission to create a repository in the target organization.
You could transfer it to another person, and they can accept. But you can't transfer it to an org.
Maybe you could transfer it to me, and then I could transfer it to Typelevel. Or maybe someone else has a better idea.
Sorry that this is a hassle. I thought it would be easy and make the project more visible.
I have a new project on discipline-specs2 that I'd like to move to munit as soon as the generator seed bug is resolved, so I'm excited to use this.
Tag me, and I'll vouch for it, and they'll set you up.
And in the meantime, I can publish. But the Sonatype folks are pretty quick.