all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>,
	"Michael Köppl" <m.koeppl@proxmox.com>
Subject: Re: [pve-devel] [PATCH dart_api_client 1/1] change exception toString to only print details if not null
Date: Wed, 21 May 2025 13:04:58 +0200	[thread overview]
Message-ID: <1d17d554-0905-4ab5-86bf-9d8d97c453a9@proxmox.com> (raw)
In-Reply-To: <20250505072845.28299-1-m.koeppl@proxmox.com>

patch looks good to me, but do you remember where you encountered this?
would make the commit message a bit better if we know how we could trigger
this (especially when trying to test this ;) )

If you want i can fix up the commit message with an example on applying

On 5/5/25 09:28, Michael Köppl wrote:
> Without this check, the toString method returns '-> null' at the end of
> the exception message if there are no details.
> 
> Signed-off-by: Michael Köppl <m.koeppl@proxmox.com>
> ---
>   lib/src/proxmox_api_exception.dart | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/lib/src/proxmox_api_exception.dart b/lib/src/proxmox_api_exception.dart
> index 8dddc7c..5c6f343 100644
> --- a/lib/src/proxmox_api_exception.dart
> +++ b/lib/src/proxmox_api_exception.dart
> @@ -7,6 +7,6 @@ class ProxmoxApiException implements Exception {
>   
>     @override
>     String toString() {
> -    return '$message -> $details';
> +    return details != null ? '$message -> $details' : message;
>     }
>   }



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel

  parent reply	other threads:[~2025-05-21 11:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05  7:28 Michael Köppl
2025-05-05 15:44 ` Shan Shaji
2025-05-21 11:04 ` Dominik Csapak [this message]
2025-05-23  7:51   ` Michael Köppl
2025-06-04 11:11 ` [pve-devel] applied: " Dominik Csapak

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=1d17d554-0905-4ab5-86bf-9d8d97c453a9@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=m.koeppl@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    /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.
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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal