From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Pettersson <daniel@dpettersson.net>
Cc: nemethf@tmit.bme.hu, 72941-done@debbugs.gnu.org, joaotavora@gmail.com
Subject: bug#72941: jsonrpc: Check if parameters are in line with the spec
Date: Sat, 12 Oct 2024 14:21:42 +0300 [thread overview]
Message-ID: <864j5hy3ax.fsf@gnu.org> (raw)
In-Reply-To: <m2ed540zxr.fsf@dpettersson.net> (message from Daniel Pettersson on Sat, 28 Sep 2024 13:40:00 +0200)
> From: Daniel Pettersson <daniel@dpettersson.net>
> Cc: Felician Nemeth <nemethf@tmit.bme.hu>, joaotavora@gmail.com,
> 72941@debbugs.gnu.org
> Date: Sat, 28 Sep 2024 13:40:00 +0200
>
> 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.
No further comments, so I'm now closing this bug.
prev parent reply other threads:[~2024-10-12 11:21 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
2024-10-02 11:41 ` Felician Nemeth
2024-10-12 11:21 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=864j5hy3ax.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=72941-done@debbugs.gnu.org \
--cc=daniel@dpettersson.net \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.