-
Notifications
You must be signed in to change notification settings - Fork 4
Move timeout to refund reason #303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -145,7 +145,6 @@ When a transaction fails, the `failureReason` field provides specific details: | |
| - `QUOTE_EXPIRED` - Quote expired before execution | ||
| - `QUOTE_EXECUTION_FAILED` - Error executing the quote | ||
| - `FUNDING_AMOUNT_MISMATCH` - Funding amount doesn't match expected amount | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Since this snippet is shared across multiple sections, consider adding a note (or a dedicated refund-reasons bullet list) indicating that - `TIMEOUT` - Transaction timed out; funds are returned as a refund with `reason: TIMEOUT`or in a separate refund reasons section: ### Refund reasons
- `TRANSACTION_FAILED` - Transaction failed after funds were sent
- `USER_CANCELLATION` - Payment cancelled by user
- `TIMEOUT` - Transaction timed out before completionPrompt To Fix With AIThis is a comment left during a code review.
Path: mintlify/snippets/error-handling.mdx
Line: 147
Comment:
**`TIMEOUT` removed but not documented as refund reason**
`TIMEOUT` is correctly removed from the outgoing failure reasons list here, but there's no corresponding mention that a `TIMEOUT` will now result in a refund with `reason: TIMEOUT`. Developers referencing this snippet after the change may not know how to handle the timeout scenario at all.
Since this snippet is shared across multiple sections, consider adding a note (or a dedicated refund-reasons bullet list) indicating that `TIMEOUT` scenarios now surface as a refund:
```mdx
- `TIMEOUT` - Transaction timed out; funds are returned as a refund with `reason: TIMEOUT`
```
or in a separate refund reasons section:
```mdx
### Refund reasons
- `TRANSACTION_FAILED` - Transaction failed after funds were sent
- `USER_CANCELLATION` - Payment cancelled by user
- `TIMEOUT` - Transaction timed out before completion
```
How can I resolve this? If you propose a fix, please make it concise.Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time! |
||
| - `TIMEOUT` - Transaction timed out | ||
|
|
||
| ### Incoming payment failures | ||
|
|
||
|
|
||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIMEOUTremoved without documenting the new refund behaviorTIMEOUTis removed from the failure reasons table, but the page gives no hint that a timeout now results in a refund. A developer reading this page would have no documentation trail explaining what happens when a transaction times out.Consider adding a brief note in the Failure Handling section, or a new "Refund reasons" table entry:
This also applies to
mintlify/snippets/error-handling.mdxline 147 where the same entry was removed.Prompt To Fix With AI