Allie Laabs

Ultimately I feel that if I write code to crash my app, it's my responsibility to handle in my code. Capturing exceptions from code the user of your module is...

I disagree with it philosophically, but it's your module! The app.error method is more than a workable solution so it's not a huge deal. I think I would appreciate it...

It's also worth noting that the general pattern you're using to throw errors that are caught locally is discouraged. So much so that WebStorm is flagging it! 

I think I figured out what the overall issue is with this implementation. It's not the global try catch necessarily - promise libraries do the same thing. It's that the...

FWIW, I'm pretty much 50/50 on my original request now that I've thought about it more, because of exactly what you said. My apps are using promises that always have...

Cool, I'll keep you updated. The context definitions could certainly be expanded to support more complex matching patterns. A string means a simple "context", but a method could manually define...

I find that structure very difficult to read. The branching on any app that requires more than a simple yes or no (good apps should allow the user to specify...

The outer element should contain the inner elements. When debugging did you keep stepping forward to see what happens in `_handle_charge_state`? That's where the VacBot logic happens to handle that...

More to the point, it seems that this issue is upstream in sleekXMPP: https://github.com/fritzy/SleekXMPP/issues/478 Considering how long that issue has been open, we may need to figure out a workaround...

The good news is that it appears that @fritzy is active again on SleekXMPP as two commits were put in today. I just left a note on the open issue...