-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
I noticed that in some cases (e.g., when slippage >= 100 or when a pool has no liquidity), the SDK also currently fails at runtime with generic errors (e.g. division by zero, undefined). These are deterministic cases that can be caught earlier and could benefit from standardized error handling.
Questions:
-
Is there a plan to introduce standardized error codes / error classes for such cases?
-
If not, would you be open to contributions (PRs) that add them? For example:
ERR_INVALID_SLIPPAGE ERR_NO_LIQUIDITY ERR_POOL_NOT_FOUND
Metadata
Metadata
Assignees
Labels
No labels