-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
unify initing processes of modes #3867
Conversation
Hey, what is needed to get this merged? |
9ad814f
to
2ded136
Compare
2ded136
to
a7e7238
Compare
@philc bump. Carret mode needed |
Bump. Is there any reason a 1 year old pr that fixes a bug is not merged yet? |
bump. plz? |
Alright folks, sorry for the delay. @gdh1995 checking in again to see what you think of this vs. #4064 (which is also now equivalent to #3877)? The use of inheritance in the implementation of modes is unnecessarily complex and I'd like to greatly simplify it at some point. #4064 is a simpler patch (3 LOC change) because it doesn't introduce new constraints around using super. I think they both fix precisely the same set of bugs, correct? |
Yes it worths to merge #4064. |
Ok great -- closing this in favor of #3877. |
BTW, I've reviewed Vimium's current code and noticed that:
|
There's a bug that some
new
-ed modes are never inited, imported when migrating from CoffeeScript to ES6. This PR fixes this by forcing subclasses ofMode
to callsuper.init()
in their constructors.This fixes #3865, fixes #3866, fixes #3926, fixes #4062 and replaces #3877.