From 857ecb7340194df69239c2f6bd85db4019e7eb77 Mon Sep 17 00:00:00 2001 From: Zachary Belford Date: Wed, 25 Sep 2019 17:08:03 -0700 Subject: [PATCH] fix: add "either" option for param structure fixes #190 partly addresses #226 Signed-off-by: Zachary Belford --- spec.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec.md b/spec.md index 9f0fe7d0..0d349765 100644 --- a/spec.md +++ b/spec.md @@ -197,7 +197,7 @@ Field Name | Type | Description servers | [[Server Object](#server-object)] | An alternative `servers` array to service this method. If an alternative `servers` array is specified at the Root level, it will be overridden by this value. errors | [[Error Object](#error-object) \| [Reference Object](#reference-object)] | A list of custom application defined errors that MAY be returned. The Errors MUST have unique error codes. links | [[Link Object](#link-object) \| [Reference Object](#reference-object)] | A list of possible links from this method call. -paramStructure | `"by-name"` \| `"by-position"` | Format the server expects the params. Defaults to `"by-position"`. +paramStructure | `"by-name"` \| `"by-position"` \| `"either"` | The expected format of the parameters. [As per the JSON-RPC 2.0 specification](https://www.jsonrpc.org/specification#parameter_structures), params may be either an array, an object, or either. Defaults to `"by-position"`. examples | [[Example Pairing Object](#example-pairing-object)] | Array of [Example Pairing Object](#example-pairing-object) where each example includes a valid params-to-result [Content Descriptor](#content-descriptor-object) pairing. This object MAY be extended with [Specification Extensions](#specification-extensions).