RFE - Errors should be different subclasses or have a code attached to them

[bpytlik]

As far as I know, if you want to handle different classes or errors coming out of node redis differently, you have to parse the error strings. For example, if I want to treat an error caused by the redis DB still loading off disk differently than I want to treat an error caused by the host being unreachable, I have to run regular expressions over the text of the error messages. That text is not a stable interface from what I can see.

There are two ways I can think of to solve this problem (and I'm sure there are many others):

1. Create different subclasses of Error and throw them instead of a generic error.
2. Add a field to the Error that's thrown and have a standard list of codes (ECONNRESET, EHOSTUNREACH, LOADINGDATA, SLAVESYNCING, etc...) which are set before the error is thrown.

This would make integrating node_redis into a larger program much easier as handling the errors would use a stable interface rather than a long text string.

If I've missed some existing mechanism to distinguish between errors, please let me know.

[brycebaril]

Sure, this would be a good enhancement. Perhaps as a model look at how http://npm.im/restify subclasses http://npm.im/verror into different error types.

[blainsmith]

In order to better support this project and its new group of collaborators under a new org we are trying to clean up and close issues older than 6 months. Your issue may have been fixed since the issue was open, however, if you are still experiencing a problem please re-open this issue and we will label it accordingly.

[bpytlik]

This is still a useful RFE in my opinion as parsing the strings in error messages is a bad interface and an interface should provide a way to differentiate between classes of errors. When I look at the code I still only see new Error(), no subclassing or codes attached so I do not think this has been fixed. Please reopen this issue.

[BridgeAR]

@bpytlik I'll reopen this if you're willing to open a pr to tackle this.

[BridgeAR]

This should get fixed by #538

[BridgeAR]

Redis error codes got added.