Repository navigation
fix: Update schema according to latest spec - #170
Conversation
|
@peol Happy to move forward with the fixes that have already landed in the spec. Otherrwise, this will have to wait until we have got things finalized there. Thank you very much for the PR, <3 |
|
@BelfordZ Sure, I'll remove |
1128ea3 to
ef91674
Compare
|
@peol If you have a chance, could you please sign your commit? Its one of the master branch protection rules for all of the open rpc repos. This is because we hope that you stick around and continue to contribute, and by signing your commits we can be sure that your next contrib is made by the same person that made this one. :) Thanks again for the PR! |
ef91674 to
cfcdf13
Compare
|
@BelfordZ Sure, I've rebased with a signed commit now :) |
|
🎉 This PR is included in version 1.7.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This PR syncs the schema with the latest documented specification (as far as I can find, at least).
x-*) on root level: https://spec.open-rpc.org/#openrpc-objectcomponents.errorsdefinition: https://spec.open-rpc.org/#components-objecteithertoparamStructure: https://spec.open-rpc.org/#method-objectAdd new componentWill be sorted in a separate PR once approach has been decidederrorGroups, as discussed here: WIP feat: error groups spec#245 — let me know if I can help move this PR forward (I've validated that it solves our issue as discussed in the issue related to the PR)Fixes #156