-
Notifications
You must be signed in to change notification settings - Fork 36
Ugly fix for plugin2 compat #78
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
Conversation
👍 |
Having learned more about plugin2 in the last 2 days fixing up D2::P::Auth::Extensible and friends I'll have a better fix in the next day or so. Will ping here when PR is updated. |
@ambs now I've finally got back to looking at this I don't really see many better ways of keeping backwards compatibility whilst working with plugin2. We could use some other method for the can check but that gains nothing. I have update the pod coverage test so it doesn't fail on the plugin2 compat layer DSL so I guess all we need now is a new release (please). 😄 |
Question: does it make sense to wait for the new plugin system to come out, and release a new version that works only with the new plugin system? Not sure if this is a silly question, i didn't look yet to your code (being really busy lately) |
On 19/01/16 17:49, Alberto Simões wrote:
P |
👍 |
Merged and released. Thanks :-) |
Excellent! This takes us past 70% of released plugins confirmed to be working with current release and plugin2. |
Thanks for your effort on this fight :) |
This is not something I'm suggesting you merge but it does work for current D2 master with zero response fix (and others) and also with latest yanick-plugins branch.