It's part of my giter8 templates github.com/devinsideyou/scala3-seed.g8 and at least in Scala3 it's less than 100 lines of code so I don't think it's worth publishing it as a library...
@@DevInsideYou your call, it would be handy though for monorepos or just those of us who don't want to add a dedicated macro module to our project. also people put out small projects, though that's obviously a matter of personal taste. if it feels too small, maybe it could be added to munit as an additional module there, an `munit-expecty` to live with `munit-scalacheck`? I'm more asking your feelings on your code being ported this way than asking you to do the work. If you were not inclined but okay with the principle, I might create the PR or ship it as a oib with vocal credit to you
I haven't evaluated zio-test yet, but if it's already a zio code base AND the team is comfortable with effectfull programming maybe zio-test is a better choice. For clean unit tests it's probably an overkill though. On the other hand it should be great if you deal with a lot of resources for example.
Thank you for sharing this code :)
this is amazing! have you considered putting it out as a library?
It's part of my giter8 templates github.com/devinsideyou/scala3-seed.g8 and at least in Scala3 it's less than 100 lines of code so I don't think it's worth publishing it as a library...
@@DevInsideYou your call, it would be handy though for monorepos or just those of us who don't want to add a dedicated macro module to our project. also people put out small projects, though that's obviously a matter of personal taste.
if it feels too small, maybe it could be added to munit as an additional module there, an `munit-expecty` to live with `munit-scalacheck`?
I'm more asking your feelings on your code being ported this way than asking you to do the work. If you were not inclined but okay with the principle, I might create the PR or ship it as a oib with vocal credit to you
Go for it.
What do you think about MUnit vs zio-test in a ZIO codebase?
I haven't evaluated zio-test yet, but if it's already a zio code base AND the team is comfortable with effectfull programming maybe zio-test is a better choice. For clean unit tests it's probably an overkill though. On the other hand it should be great if you deal with a lot of resources for example.