docs(specs): update OpenRPC specifications from Daikon [Bot]#1148
docs(specs): update OpenRPC specifications from Daikon [Bot]#1148alchemy-bot wants to merge 8 commits intomainfrom
Conversation
🔗 Preview Mode
|
|
test |
![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: 45a34e88d2
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| ../_components/polkadot/methods.yaml#/components/methods/chain_getFinalizedHead | ||
| - $ref: ../_components/polkadot/methods.yaml#/components/methods/chain_getHeader |
There was a problem hiding this comment.
These two new Astar methods resolve through ../_components/polkadot/methods.yaml, but there is no src/openrpc/chains/_components/polkadot/ directory in this repo. From a clean checkout, generate-rpc cannot dereference the Astar schema, so the chain_* endpoints added by this PR never make it into the generated spec or docs.
Useful? React with 👍 / 👎.
| ../_components/pchain/methods.yaml#/components/methods/platform.getAllValidatorsAt | ||
| - $ref: ../_components/pchain/methods.yaml#/components/methods/platform.getBalance |
There was a problem hiding this comment.
The new platform.* refs are pointing at ../_components/pchain/..., but this tree only contains src/openrpc/chains/_components/avalanche-p/ (the standalone avalanche-p spec already uses that path). With the path as written here, the Avalanche OpenRPC spec cannot dereference these additions, so the new P-chain endpoints will be missing from generated docs.
Useful? React with 👍 / 👎.
| ../_components/tron/methods.yaml#/components/methods//wallet/accountpermissionupdate | ||
| - $ref: ../_components/tron/methods.yaml#/components/methods//wallet/broadcasthex |
There was a problem hiding this comment.
These new /wallet* methods all depend on ../_components/tron/methods.yaml, but there is no src/openrpc/chains/_components/tron/ directory in the repository. On a clean build the Tron OpenRPC schema can no longer be dereferenced, so the overview links added in this PR won't have generated endpoint pages behind them.
Useful? React with 👍 / 👎.
| - $ref: ../_components/celestiabridge/methods.yaml#/components/methods/blob.Get | ||
| - $ref: ../_components/celestiabridge/methods.yaml#/components/methods/blob.GetAll |
There was a problem hiding this comment.
This new chain starts by dereferencing ../_components/celestiabridge/methods.yaml, but no such component file exists under src/openrpc/chains/_components/. That means the CelestiaBridge spec cannot be generated from a clean checkout, so the new api-name: celestiabridge section added in content/docs.yml will have no backing API spec to index.
Useful? React with 👍 / 👎.
|
|
||
| ## CelestiaBridge APIs | ||
|
|
||
| 📙 Get started with our [CelestiaBridge API Quickstart Guide](/docs/reference/celestiabridge-api-quickstart). |
There was a problem hiding this comment.
This CTA points to /docs/reference/celestiabridge-api-quickstart, but a repo-wide search only finds this single reference—there is no MDX page or redirect for that slug. As shipped, the new CelestiaBridge overview sends readers to a 404 for the primary getting-started link.
Useful? React with 👍 / 👎.
2 participants
🤖 Automated update of OpenRPC specs
This PR updates JSON-RPC method references based on the latest Daikon config. See this comprehensive guide
44 chains created or updated:
This workflow run:
Something look wrong? If you are an Alchemy employee please open a PR with changes in Daikon. If you are a member of the public please reach out to our team.