-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Register plugin into registry #838
Conversation
* remove original plugin dictionaries and replace them with registry * move registries for parser/formatter to plugin.rb
case | ||
when obj.is_a?(Class) | ||
obj.new | ||
when obj.respond_to?(:call) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The number of arity check is needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct. Better to have.
@repeatedly Can I merge after fixes of your points? |
Yes. @sonots Could you also check this? |
* custom plugin directly must be able to override built-in files
LGTM |
OK. I'll merge this after green (Travis is already ok. Waiting appveyor). |
An Appveyor task in a job is failing weird error and there's no way to rebuild it... I'll merge this :P |
Register plugin into registry
To make straightforward dependencies from kinds of plugins to plugin.rb, and reduce duplicated implementation between plugin.rb and registry.rb.