docs(specs): update OpenRPC specifications from Daikon [Bot]#1457
Conversation
🔗 Preview Mode
|
![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: 2c9eeb239c
ℹ️ 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".
| - $ref: ../_components/custom/methods.yaml#/components/methods/eth_getCodeByHash | ||
| - $ref: ../_components/custom/methods.yaml#/components/methods/eth_getHeaderByHash | ||
| - $ref: >- | ||
| ../_components/custom/methods.yaml#/components/methods/eth_getHeaderByNumber |
There was a problem hiding this comment.
All three new fragment targets are absent from src/openrpc/chains/_components/custom/methods.yaml. generateOpenRpcSpec dereferences this file before writing content/api-specs/chains/megaeth.json, so the unresolved references cause the MegaETH RPC generation to report an error and prevent the updated API spec (and therefore the newly linked endpoint pages) from being produced. Add the component definitions or point these entries at an existing source.
Useful? React with 👍 / 👎.
1 participant
🤖 Automated update of OpenRPC specs
This PR updates JSON-RPC method references based on the latest Daikon config. See this comprehensive guide
1 chain 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.