You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for updating MG to ES6 modules. Congrats on the release. I've been following the announcement discussion. I plan on contributing to your fork.
Looking at the API, I'm wondering if or how you'd like to implement MG2 plugin / modules? Do you have a module architecture in mind?
Naturally legacy MG plugins would need to be rewritten, which provides like an opportunity to define a class loader (ie, prior to instantiating LineChart). I have a few ideas, but wanted to open a ticket for discussion.
Side note, I've added support for MG lifecycle events / hooks (as defined in common/hooks.js): add_hook and call_hook methods. This would likely impact modules, which often depend on hooks (ie, line.after_init). Interested in a PR?
The text was updated successfully, but these errors were encountered:
Thank you for updating MG to ES6 modules. Congrats on the release. I've been following the announcement discussion. I plan on contributing to your fork.
Looking at the API, I'm wondering if or how you'd like to implement
MG2
plugin / modules? Do you have a module architecture in mind?Naturally legacy MG plugins would need to be rewritten, which provides like an opportunity to define a class loader (ie, prior to instantiating
LineChart
). I have a few ideas, but wanted to open a ticket for discussion.Side note, I've added support for MG lifecycle events / hooks (as defined in
common/hooks.js
):add_hook
andcall_hook
methods. This would likely impact modules, which often depend on hooks (ie,line.after_init
). Interested in a PR?The text was updated successfully, but these errors were encountered: