Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:124102 X-Original-To: internals@lists.php.net Delivered-To: internals@lists.php.net Received: from php-smtp4.php.net (php-smtp4.php.net [45.112.84.5]) by qa.php.net (Postfix) with ESMTPS id 6CB301ADAA7 for ; Sun, 30 Jun 2024 14:52:22 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=php.net; s=mail; t=1719759222; bh=25ciPK4/WGycmQ9RYFcf6HQByrMRgMosFrr0i5rLaRY=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=Ca+UmWrQFnfTXrw4NHKyP+hUXXAreFop8RP5Zf29agVGR56uBlFcuGTVi5lD20cid wyANYESZcCGG87iT3G7jCq1bCICkgK1EQcphQnkWZ3at+H0kIjK+EypX1Fgoz6rDqa t9/pa4SZyaqy74FXJXdR8ZouUB73+SoNpkwSO/3OLlIs+D0bNq8zWTusTJ/eu5eRXi 8CnJ6ADGvweCVd3jncs7R7E0egiAc2nkd39YW+Kd4WoJNeA3qdhU9GFFeqYr4qukVB tJbYkhXDnNcKbarCJKb+OLAcUeFapzsYa4T4jIH6FF82VcP6EJrEcPRtbz1Npibk0E LGRYal7mH9H7A== Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 69023180BB1 for ; Sun, 30 Jun 2024 14:53:40 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,DMARC_PASS,FREEMAIL_FROM, HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=4.0.0 X-Spam-Virus: Error (Cannot connect to unix socket '/var/run/clamav/clamd.ctl': connect: Connection refused) X-Envelope-From: Received: from mail-ua1-f43.google.com (mail-ua1-f43.google.com [209.85.222.43]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sun, 30 Jun 2024 14:53:38 +0000 (UTC) Received: by mail-ua1-f43.google.com with SMTP id a1e0cc1a2514c-80f9e894b7eso614603241.2 for ; Sun, 30 Jun 2024 07:52:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719759137; x=1720363937; darn=lists.php.net; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=25ciPK4/WGycmQ9RYFcf6HQByrMRgMosFrr0i5rLaRY=; b=TCRgz4Qcip7/Kdq/6BB9xmkjHoDxI08vfspqfOd/K+B0o6J0vopgvYsXluoTK0rW3b LwmY9yt4QC3XlWBtioPSxw6VrNHLkf8zy2104eJTFZcw9Qq1g7wDhVd96Ueoe4yP5XM/ uEOf/AgpPRtrbc1P4LP2f/zfz8fkWhU87eQ5RqFnqZB8MHAdwRNC3cPYcS7v7zwR/6x0 sEpRjyYrxXoD35nkycCAYvTFPqXwRRLNbyxp5KGX/ER/hzlK+/2+wy8SDGBYqOA9flQM wYnVQOvVV39SdJbPRJD7/D9hs44b6kHnghwJ7wID89nmPK/DduITLnJcxS9NTZAcGEtn 34pQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719759137; x=1720363937; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=25ciPK4/WGycmQ9RYFcf6HQByrMRgMosFrr0i5rLaRY=; b=hrueY3cxtdEY3njd9VRAehEMo3btSCJCUFZZbZn2bb0gWgyUWkuEuCG0dJtml/0pXu 8OO/FRJrSlcWDpx0efw6DKjHw5U+eRjyX8ckwaq0ENhisf9+lg3bdUXG23jB6PPpmSQw l9KvOR2vDLz8AV3qFcsraFJDnDUAGnVeGLAlcfgnb1gpGJ14PmTThPvPYcW2vvFtBFx/ InA1pIWSZ7xWrhtEqg9bnBbkNLz5jumgBiJ1DsPKZRKbm4aqXS9B7Jj3S0gYXKNu/n1j pp7TvYBIL7W6uvmxqAtD+RIPIzoLmsoo/BXvzZICIMCtEwPu6y/TCMcaBjsEwwuLUl1Q q4gw== X-Forwarded-Encrypted: i=1; AJvYcCX6G0XvCZ1mebYOgQv5c/BK2xs21/0+1WQTIP/gFnoP+hHOIkr+BnutCncyqfsQKzV6wfKoJisegDRFN2YZT43EdZubeGI4VQ== X-Gm-Message-State: AOJu0YwoIOSsHiD8vAl2LkUTYymYwUCpAgN9+guZ4ap7+obBgtOIwPSO XW5ZQZdzq4KB4u94YWP8g3pEUOEe+iEdsOKOg7pEFY8ITGqs5avOBjoJ/tAtMBmJecQApDqqkOB 9broZwIZOtLz0MiRlLzlCYj9/3Fjclw== X-Google-Smtp-Source: AGHT+IElIMVIS4Lc0rUcDOwkVuA1CswvM6hhvB4AGePlip6w4AkvouOWSNHI6LGHH6DP5uPEOdcIGJUw9KeCa9tLdxU= X-Received: by 2002:a05:6122:608a:b0:4ef:6530:4ced with SMTP id 71dfb90a1353d-4f2a563e56bmr3690035e0c.2.1719759137506; Sun, 30 Jun 2024 07:52:17 -0700 (PDT) Precedence: bulk list-help: list-post: List-Id: internals.lists.php.net MIME-Version: 1.0 References: <66420855-9900-48a8-9964-b9dda81a8bdc@bastelstu.be> In-Reply-To: Date: Sun, 30 Jun 2024 11:52:06 -0300 Message-ID: Subject: Re: [PHP-DEV] [RFC][Discussion] Enhance JSON error messages To: =?UTF-8?Q?Tim_D=C3=BCsterhus?= Cc: "Gina P. Banyard" , PHP Internals List Content-Type: multipart/alternative; boundary="0000000000007d8db5061c1ca0a9" From: dev.juan.morales@gmail.com (juan carlos morales) --0000000000007d8db5061c1ca0a9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable El El dom, 30 de jun. de 2024 a la(s) 11:15, Tim D=C3=BCsterhus escribi=C3=B3: > Hi > > On 6/30/24 15:43, juan carlos morales wrote: > > So, what I see here in my shortexperiencie is an RFC with 3 Options > > That is not an option. Each RFC needs a clear primary vote that is a > "Yes/No" vote. > > > 1) Enhance the error message we already have > > > > 2) keep json_last_error_msg as it is and add a new function > > json_last_error_info function > > > > 3) both > > > > Adjusting error messages to make them better is not something that > requires an RFC. We do this all the time without an RFC. Here's an > example PR: https://github.com/php/php-src/pull/14496 > > A new json_last_error_info() for easier programmatic access of the > important bits can still be considered, but would not need an RFC either > from my point of view. It's a simple and obvious addition. Those can be > done without an RFC, unless someone complains. > > Best regards > Tim D=C3=BCsterhus > Ok , then, i will prepare 2 PRs and lets see what happens then. Thanks. I will let everybody know When ready --0000000000007d8db5061c1ca0a9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


El El dom, 30 de jun. de 2024 a la(s) 11:15, Tim D=C3=BCste= rhus <tim@bastelstu.be> escri= bi=C3=B3:
Hi

On 6/30/24 15:43, juan carlos morales wrote:
> So, what I see here in my shortexperiencie is an RFC with 3 Options
That is not an option. Each RFC needs a clear primary vote that is a
"Yes/No" vote.

> 1) Enhance the error message we already have
>
> 2) keep json_last_error_msg as it is and add a new function
> json_last_error_info function
>
> 3) both
>

Adjusting error messages to make them better is not something that
requires an RFC. We do this all the time without an RFC. Here's an
example PR: https://github.com/php/php-src/pull/14496
A new json_last_error_info() for easier programmatic access of the
important bits can still be considered, but would not need an RFC either from my point of view. It's a simple and obvious addition. Those can be=
done without an RFC, unless someone complains.

Best regards
Tim D=C3=BCsterhus
=

Ok ,= then, i will prepare 2 PRs and lets see what happens then.

Thanks.

I will let everybody know When ready
--0000000000007d8db5061c1ca0a9--