-
-
Notifications
You must be signed in to change notification settings - Fork 102
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
What about Version 2 #173
Comments
Hey, on my end I have no plans on working on v2. Maybe @theofidry has some plans? (and btw there's no problem if there are no plans to continue that at the moment) |
is there currently a workaround for #101 in v1? |
Hello, I was wondering the same as I'm still using an old fork because of this specific issue. Maybe I could send a new PR with the same code as #101, without the BC break on What do you think ? |
@fsevestre that would be nice |
Finally got some time to work on this :) #175 |
how is version 2 commits older than version 1 ? |
Hello, i am wondering if there is going to be a release of version 2.
It seems the branch has not really gotten a lot of attentien.
mainly i am asking because i need this pr: #101
Maybe i just did not see how this can be done on version 1, but as i understand it this can not be achieved currently in version 1.
The text was updated successfully, but these errors were encountered: