-
Notifications
You must be signed in to change notification settings - Fork 32
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
fidget 2? #125
Comments
Yes I am working on fidget 2, I am taking a slightly different approach so it's a complete rewrite. I will be releasing it when it's ready. I will not be putting more work into fidget 1. |
@treeform Is fidget 2 going to be in the same package or will it be separate? |
I am not sure. It's currently a separate repo. But it might be nice to keep a simpler name. |
So... this still holds?, because I see new cool work being done on fidget1, but you said that you will not work on 1 anymore, |
We only updated some deps in fidget1, most work is being done in fidget 2. |
Personally I say merge it into this repo once ready. Fidget has nearly 500 github stars and is just an awesome name in my opinion 💪 At least I will subscribe to the release channel of this repo and wait :D |
+1. Merge the repo and use the versioning system. It's better for the visibility of the project. It's IMHO perfectly fine to justify a rewrite after a major version change. And people who wants to use fidget1 can still specify the version range they wish to use. |
Sounds, good I will put the v2 code into this repo when its ready. |
I read in a comment of an open pull request, that you're working on a fidget 2 already? Is there any more detailed information on that?
The text was updated successfully, but these errors were encountered: