If we're gonna use exceptions, the best practice is to define some custom-named ones so that ours can be told from everyone else's (by both humans and machines).
Lower priority, but opening the issue now so we at least have it.
If we're gonna use exceptions, the best practice is to define some custom-named ones so that ours can be told from everyone else's (by both humans and machines).
Lower priority, but opening the issue now so we at least have it.
Comments
Comment #1
marvil07 commentedWe are mainly doing it now after recent sync-related topic branches, but we are still throwing many simple php exceptions.
Comment #2
sdboyer commentedthis is just a silly meta-ish issue to have open, i think. we should create such exceptions as we go, as needed. this doesn't make sense to have as its own issue.
closing it.