docs: add relay integration guide - #824
Conversation
|
@brendanjryan is attempting to deploy a commit to the Tempo Team on Vercel. A member of the Team first needs to authorize it. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d656124b52
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| Client->>API: Request | ||
| API-->>Client: 402 + Challenge | ||
| Client->>API: Retry + Credential | ||
| API->>Relay: [!emphasis] Validate Credential |
There was a problem hiding this comment.
When Vocs publishes this page as Markdown, mermaidDiagram() passes the chart through verbatim, so [!emphasis] remains inside the standard mermaid fence and renders as literal label text instead of emphasis. Strip the custom markers in the Markdown renderer and add a focused renderer test so the published diagram remains semantic.
AGENTS.md reference: AGENTS.md:L324-L327
Useful? React with 👍 / 👎.
| export const charge = Method.toServer(Methods.charge, { | ||
| async validate({ credential, request }) { |
There was a problem hiding this comment.
broadcast before validate
In this new Method.toServer options object, validate precedes broadcast, contrary to the repository-required alphabetical ordering for object properties in documentation examples. Move the complete broadcast hook before validate so the copyable example follows the documented convention.
AGENTS.md reference: AGENTS.md:L291-L294
Useful? React with 👍 / 👎.
1 participant
Motivation
Document relay-based payment validation and finalization for mppx users and relay authors.
Summary
Key design considerations