Bug 41728: (QA follow-up) Declare issue and patron variables together

There seems to be no reason to declare $patron near the start of the sub
while $issue is declared where they are both populated.

Signed-off-by: Kyle M Hall <kyle@bywatersolutions.com>
Signed-off-by: Martin Renvoize <martin.renvoize@openfifth.co.uk>
Signed-off-by: Tomás Cohen Arazi <tomascohen@theke.io>
Signed-off-by: Martin Renvoize <martin.renvoize@openfifth.co.uk>
Signed-off-by: Pedro Amorim <pedro.amorim@openfifth.co.uk>
This commit is contained in:
Kyle M Hall 2026-04-07 14:49:33 -04:00 committed by Pedro Amorim
parent dad9fd4a30
commit 2e4459ea69
No known key found for this signature in database
GPG Key ID: 06B75BA7F3894D55
1 changed files with 1 additions and 1 deletions

View File

@ -2442,7 +2442,7 @@ sub AddReturn {
# Extract context objects
my $issue = $availability->context->{checkout};
$patron = $availability->context->{patron};
$patron = $availability->context->{patron};
# Set NotIssued message if item not checked out
if ( !$issue ) {