We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://swagger.io/specification/
This specification if used makes the description compatible with many more open source tools
Just wondering why the format was invented rather than writing something that exists to describe APIs and has a JSON schema defined already
Came across this repo because I wrote a JSON schema for a lot of the Ethereum RPC objects https://unpkg.com/@ethercast/model@latest/build/ethereum-types-schema.json
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Issue Type
Description
https://swagger.io/specification/
This specification if used makes the description compatible with many more open source tools
Just wondering why the format was invented rather than writing something that exists to describe APIs and has a JSON schema defined already
Came across this repo because I wrote a JSON schema for a lot of the Ethereum RPC objects
https://unpkg.com/@ethercast/model@latest/build/ethereum-types-schema.json
The text was updated successfully, but these errors were encountered: