-
Notifications
You must be signed in to change notification settings - Fork 32
Open
Description
When bch-js receives a 429 error from bch-api, it sometimes returns the error message as an object, rather than throwing an error. The proper behavior is to throw an error.
The scope of this Issue is to review the error handlers of endpoints and properly handle 429 errors. This code snippet of validateTxid3() captures how it catches and properly handles 429 errors:
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels