call plugin onChange method

[hosmelq]

No description provided.

[juliankrispel]

@hosmelq I actually think removing onChange from plugin methods simplifies the API. It's also little bit confusing, like - as a user I'm not sure if this means I'm listening to events or updating the state, in the previous versions of plugins this is both - which is imo super confusing.

I don't think it's needed really...

[hosmelq]

Perfect, I like the idea. You can close this whenever you want.

[juliankrispel]

Sweet. Hey btw if you’re interested in contributing maybe we could pair sometime? If you’re down ping me on slack or twitter plz 👍

…

On Wed, Oct 3, 2018 at 5:04 AM Hosmel Quintana ***@***.***> wrote: Perfect, I like the idea. You can close this whenever you want. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#3 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABIhWvE41t5x64gPZiaBueWer-llbiBBks5uhDdrgaJpZM4XDTIg> .

[hosmelq]

Gracias @juliankrispel, no sé mucho sobre borrador, pero podría ayudar. 🙂