Summary: | Koha::Biblio->record does not return items | ||
---|---|---|---|
Product: | Koha | Reporter: | Janusz Kaczmarek <januszop> |
Component: | Architecture, internals, and plumbing | Assignee: | Janusz Kaczmarek <januszop> |
Status: | RESOLVED INVALID | QA Contact: | Testopia <testopia> |
Severity: | minor | ||
Priority: | P5 - low | CC: | dcook, pedro.amorim, tomascohen |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | Sponsored | Patch complexity: | Trivial patch |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: | |||
Bug Depends on: | 33083 | ||
Bug Blocks: | |||
Attachments: |
Bug 38033: Koha::Biblio->record does not return items
Bug 38033: Koha::Biblio->record does not return items |
Description
Janusz Kaczmarek
2024-09-30 11:52:26 UTC
Created attachment 172221 [details] [review] Bug 38033: Koha::Biblio->record does not return items Koha::Biblio->record introduced by Bug 33083 seems to be a straigtforward alias for Koha::Biblio::Metadata->record but it does not pass the parameters to $self->metadata->record call. This may lead to misunderstandings and possible bugs. The provided patch corrects this issue. Use unit test to test. Sponsored-by: Ignatianum University in Cracow Use case: one would expect $biblio->record({ embed_items => 1 }) returns the linked items (as it does $biblio->metadata->record({ embed_items => 1 }) ) -- but unfortunately now it does not. Created attachment 172237 [details] [review] Bug 38033: Koha::Biblio->record does not return items Koha::Biblio->record introduced by Bug 33083 seems to be a straigtforward alias for Koha::Biblio::Metadata->record but it does not pass the parameters to $self->metadata->record call. This may lead to misunderstandings and possible bugs. The provided patch corrects this issue. Use unit test to test. Sponsored-by: Ignatianum University in Cracow Signed-off-by: Roman Dolny <roman.dolny@jezuici.pl> This is an interesting one. Probably should have a different title, but looking at the code... it seems pretty reasonable. We are headed toward bug 31224 instead of this. (In reply to Tomás Cohen Arazi (tcohen) from comment #5) > We are headed toward bug 31224 instead of this. Setting as RESOLVED INVALID. |