spec

spec copied to clipboard

zcstarr

should use `https://json-schema.org/draft/2020-12/json-schema-core.html#section-8.2.3`

BelfordZ

Examples should allow error results

5

This would also make automated testing tools able to test against failing cases.

BelfordZ

Feature: Re-using params for several methods

4

Hi! For our methods, we have multiple common params for each method, let's call them `Username` and `Password`. So if we have 100 methods, we are for each one required...

pontus-eliason

Seems open-rpc spec does not support error examples

2

Pana

Is there a more elegant way to define "no result" for a method

11

In my API I have some functions that do not return a result. I implement this by responding with a "null" value (but a "true" is just as good). The...

ricktaylor

Add description for errors

4

A description field could be helpful for adding some additional information to the errors that doesn't necessarily end up going over the wire: what the error means, when and why...

bevalorous

Allow multiple input/output signatures for the same method name

4

#### Problem In the docs for `Method` it is written: > The method name is used as the method field of the JSON-RPC body. It therefore MUST be unique. Consider...

steveluscher

Does OpenRPC supports something like "discriminator" for oneOf and anyOf?

2

OpenAPI supports it and this feature is useful when writing code-generated API wrappers. Here is how it looks like in the OpenAPI spec: ```yaml components: responses: sampleObjectResponse: content: application/json: schema:...

svetlyak40wt

Creating constraints between parameters

1

We should have a way to support 1 param determining the type of another param. ie assume I have the following api: ``` name: "bar", params: [ { name: 'foo'...

BelfordZ