-
Notifications
You must be signed in to change notification settings - Fork 6
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
Possible deprecation? #164
Comments
Hi @kubukoz, That's probably a very good idea as I'm not really writing Scala at the moment. Thanks for the heads up in the alternative. |
@nevillelyh would you be interested in taking refugees from this repository? ;) Can you confirm whether there are plans to support future Scala versions in magnolify? |
I think it's a safe assumption that either Magnolify will support Scala 3 once Magnolia is able to, or people will just build their own thing. Since neither you nor I have enough time to develop this one (and there's probably no need to, since there's a living alternative), I propose we archive this repository and direct people there :) |
I'll update @scala-steward . |
Sorry just saw this. We'll support these type class derivation for scala 3 in some form, either natively or via magnolia. Also happy to consolidate things from this lib into ours. File issues in magnolify for anything you can think of? |
Hi @ChocPanda,
Personally I have been using https://github.com/spotify/magnolify's scalacheck module for a while instead of this project. They have both Arbitrary and Cogen derivation, and the project is maintained under a company's umbrella, which makes it look like it'll be there for a while.
Given that scalacheck-magnolia hasn't had much development recently, and that there's a new Scala version coming, I would consider deprecating the project and suggesting that new users use Magnolify instead.
What do you think?
The text was updated successfully, but these errors were encountered: