| Summary: | VueJS: We should abandon type="vendor" resource attribute | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Pedro Amorim <pedro.amorim> |
| Component: | Architecture, internals, and plumbing | Assignee: | Bugs List <koha-bugs> |
| Status: | In Discussion --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | jonathan.druart, martin.renvoize, matt.blenkinsop, pedro.amorim |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
| Attachments: | Bug 41275: Drop vendor in favor of relationshipSelect | ||
|
Description
Pedro Amorim
2025-11-19 17:27:09 UTC
Created attachment 189717 [details] [review] Bug 41275: Drop vendor in favor of relationshipSelect This is only a PoC for AgreementResource. More are needed. Type = 'vendor' was a measure taken at the time to solve the issue immediatelly, but we have since abstracted 'simple' relationships to use relationshipSelect and there's no reason to continue using type: 'vendor'. The thing I'd like comments on here is that an API call is done by relationshipSelect, whereas before the vendors were coming from the vendorStore loaded in ERM. AFAIK, this vendorStore load in ERM is still required to populate the 'vendor' table column filter options. Thoughts? Could the table column not just be a searchable column rather than needing all vendors loading into a dropdown? |