TJ
TJ
we definitely _have_ to be flexible, but I think we can do magic, and retain the flexibility
that's the idea, it would basically just expand at the API level, so something like `resource('profile')` would make a call to say `singularResource('profile')` similar, allowing the call to be explicit...
yup, that's the plan
when I have time im going to adapt superagent for testing frameworks, it'll be much more flexible
unfortunately the only way to be 100% sure that an exit will occur on an error (due to open db connections etc) is to explicitly invoke process.exit(), which might not...
no specific reason, I'd be fine with changing that. I'm ok with bits and pieces to support >IE8 and friends, just nothing huge and unwieldy
ah damn it's v2, which seems broken :'(
I just get `Name already registered with serializer`, which seems to still be an open bug
yeah definitely sucks :( I have mixed feelings about adding a root level error handler, it's sort of necessary in this case but then it deviates from the norm, and...
I don't want to form too many opinions based on the current stream implementation since they're super broken. We have a few choices for future stuff I guess, people can...