>> Would it be possible to extend jsonrpc.el to check the params argument >> of jsonrpc-request, jsonrpc-notify, and jsonrpc-async-request whether it >> is a structured value? And if it is not, then guide the programmer to >> the above URL with a warning.
The use case makes sense to me, but I would go with updating the docs rather then the API. The current wording could use some love as it's refereed to as JSON object or plist (at different functions). When it should be plist or vector, where we could throw in a link to the specification. I am not for signaling an error or similar as it's a breaking change in my book, which does not seam called for in this case. /Daniel Pettersson
