-
Notifications
You must be signed in to change notification settings - Fork 59
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
Plugin architecture #7
Labels
Comments
Yeah, I was thinking about it while working on the redux implementation. It would be great to have the method inside the core and then extend form that if needed. We should define what the plugin should export, in order to create consistency between plugins and to provide naive example: export function myAwesomePlugin (routerInstance) {
// do something with the router instance
} so // inside the UIRouter class
plugin = (pluginToApply) => {
pluginToApply(this);
} |
@elboman
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With visualizer, sticky states, dsr, etc. it might be nice to have an official plugin architecture.
Something like:
The text was updated successfully, but these errors were encountered: