-
Notifications
You must be signed in to change notification settings - Fork 23
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
Null Safety #15
Comments
Fixed by #13 |
Any news on this? |
Hi, any update? |
@calvintam236 true. It seems there are not many updates happening on this package anymore. If @Skquark @mendieta don't have time, someone could join the maintainers to be able to merge PRs and release new versions. |
If they are not going to response soon, I think it is a good time to start a community fork |
@calvintam236 exactly |
Should it be called tinycolor 2 2 or tinycolor 3? 🤔 |
Current version is v1.0.3 so
Node.js side: https://www.npmjs.com/package/tinycolor2 |
@calvintam236 should I go ahead and fork the repo? I can add you as co-maintainer... |
Sure. That works for me. You can do it under an organization since it is community based. |
@calvintam236 I think I'd first fork it on my personal account and then in a second step propose it e.g. to fluttercommunity organization. Except you already have some organization!? |
https://github.com/fluttercommunity/community#note-to-packages-owners Let’s create an organization for this project, maybe |
Hey all, community-forked repo is live now. Please feel free to contribute PRs while we are working to update the code and publish to pub.dev. |
Hi, Any news on this? |
@manukumarsb7 check this |
Hi @WieFel @calvintam236 When you guys are planning to publish null safety update on pub.dev ? |
@rkoshti it is already released for some time. Be aware that therefore you have to use our new package |
Thanks for the great package!
Do you plan to make a null safe update of the package?
The text was updated successfully, but these errors were encountered: