unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Pettersson <daniel@dpettersson.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Felician Nemeth <nemethf@tmit.bme.hu>,
	72941@debbugs.gnu.org, joaotavora@gmail.com
Subject: bug#72941: jsonrpc: Check if parameters are in line with the spec
Date: Sat, 28 Sep 2024 13:40:00 +0200	[thread overview]
Message-ID: <m2ed540zxr.fsf@dpettersson.net> (raw)
In-Reply-To: <86tte06u7i.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 28 Sep 2024 11:47:13 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

> So do we want to close this as wontfix?

Yes, if anybody would clarify the variable type expectations
documentation that would be great but all in all this is would be
wontfix.

>> From: Felician Nemeth <nemethf@tmit.bme.hu>

>> Maybe when the server responds with an error to a jsonrpc-request, then
>> jsonrpc.el could create an additional warning if the params of the
>> request was not structured.  Or maybe it is too much work for a very
>> small gain.

It seams like something that would be a bit of mess and I would expect
that an sane jsonrpc server would include the reason for error in the
error response.






  reply	other threads:[~2024-09-28 11:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-01 16:26 bug#72941: jsonrpc: Check if parameters are in line with the spec Felician Nemeth
2024-09-02 11:26 ` Eli Zaretskii
2024-09-05 20:35   ` Daniel Pettersson
2024-09-13 17:13     ` Felician Nemeth
2024-09-28  8:47       ` Eli Zaretskii
2024-09-28 11:40         ` Daniel Pettersson [this message]
2024-10-02 11:41           ` Felician Nemeth
2024-10-12 11:21           ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2ed540zxr.fsf@dpettersson.net \
    --to=daniel@dpettersson.net \
    --cc=72941@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=nemethf@tmit.bme.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).