@bendrucker saw your downvote, any thoughts on https://github.com/yoshuawuyts/choo/issues/152#issuecomment-232146705 … ?
-
-
Replying to @yoshuawuyts
I’m +1 on supporting other async APIs but otherwise expanding the model API this early is bad
1 reply 0 retweets 1 like -
Replying to @bendrucker
yeah, wouldn't want to expand the model API hey - what do you think of streamlining plugin usage through app.use() ?
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts @bendrucker
e.g. not exposing new functionality, just allow multiple handlers to be plugged into the same hooks
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
At that point why not just `app.onState(listeners…)`?
1 reply 0 retweets 0 likes -
Replying to @bendrucker
something like a logger attaches itself to several hooks; matching each plugin to its hooks probs leads to boilerplate and errs
1 reply 0 retweets 0 likes -
replicating to localstorage / indexdb would be another one; also wrapping async to allow first-class pull-streams is another
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.