Back to bug 38201

Who When What Removed Added
pedro.amorim 2024-10-18 08:26:04 UTC CC jonathan.druart, martin.renvoize, matt.blenkinsop, paul.derscheid, pedro.amorim
URL https://github.com/PTFS-Europe/koha/tree/b_38201
Status NEW In Discussion
pedro.amorim 2024-10-18 09:13:11 UTC See Also https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37930
dcook 2024-10-20 22:32:39 UTC CC dcook
pedro.amorim 2024-12-16 12:33:05 UTC Blocks 37893
pedro.amorim 2025-01-27 12:09:38 UTC URL https://github.com/PTFS-Europe/koha/tree/b_38201 https://github.com/PTFS-Europe/koha/tree/new_bug_38201
pedro.amorim 2025-02-14 12:56:46 UTC See Also https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37301
Depends on 37301
jacob.omara 2025-03-03 10:59:11 UTC Blocks 39224
pedro.amorim 2025-03-13 12:23:26 UTC Blocks 39320
lucas 2025-04-01 08:14:02 UTC CC lucas
lisette 2025-04-01 08:14:09 UTC CC lisette
Laura.escamilla 2025-04-01 08:14:16 UTC CC Laura.escamilla
michael.skarupianski 2025-04-01 08:15:04 UTC CC michael.skarupianski
lisette 2025-04-01 08:43:40 UTC URL https://github.com/PTFS-Europe/koha/tree/new_bug_38201 https://github.com/openfifth/koha/tree/new_bug_38201
matt.blenkinsop 2025-04-07 09:37:00 UTC Blocks 39571
esther.melander 2025-04-08 16:07:28 UTC CC esther.melander
jonathan.druart 2025-06-24 09:25:36 UTC See Also https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40191
jonathan.druart 2025-06-24 10:03:19 UTC See Also https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34417
jonathan.druart 2025-07-24 08:04:20 UTC Depends on 40483
matt.blenkinsop 2025-07-25 08:18:41 UTC Depends on 40511
matt.blenkinsop 2025-07-25 08:35:24 UTC Depends on 40511 40512
michaela.sieber 2025-07-31 08:06:23 UTC CC michaela.sieber
michaela.sieber 2025-07-31 08:19:57 UTC Depends on 38446
jonathan.druart 2025-07-31 09:45:18 UTC Status In Discussion Needs Signoff
jonathan.druart 2025-07-31 09:45:33 UTC Assignee koha-bugs matt.blenkinsop
QA Contact testopia jonathan.druart
jonathan.druart 2025-07-31 13:44:18 UTC Blocks 38311
michaela.sieber 2025-07-31 17:20:11 UTC Status Needs Signoff Failed QA
lucas 2025-09-23 12:05:48 UTC Keywords RM_priority
michaela.sieber 2025-09-23 16:36:28 UTC Status Failed QA Needs Signoff
michaela.sieber 2025-09-23 16:39:35 UTC Status Needs Signoff Signed Off
matt.blenkinsop 2025-09-25 14:09:31 UTC Blocks 40878
jonathan.druart 2025-09-26 09:36:44 UTC Keywords release-notes-needed
matt.blenkinsop 2025-09-26 10:45:48 UTC Depends on 40809
matt.blenkinsop 2025-10-02 08:22:48 UTC Text to go in the release notes The idea behind this bug was to introduce a framework for building Vue applications and components that would allow a developer to make use of pre-existing components and logic, rather than having to write everything from scratch. Currently in Koha, as they render the different input and display options in a standardised manner. These are made use of by ResourceFormSave requirements. However, the goal is that if the developer feels that there could be a need for that requirement in future for someone else, as well as a standardised ‘list’ component. This means that each new Vue module can be built very quickly without the need to write out all the HTML structure and logic for creating a form/display page - the developer can simply access the pre-written may need it.

Moving forwards, we have a lot of bespoke logic for each different form/display page as well as a lot of repeated code. This can make regressions more likely and reduce code consistency. To address this, ResourceShow and ResourceList which act as generic components that can be used by the developer to handle any Koha data type. To prove this, all the existing Vue modules (ERM, Preservation, then the goal should be to expand the framework to support it so that all can benefit. We have documented this through the use of JSDoc in base-resource.js
Keywords release-notes-needed
Text to go in the release notes logic in the framework to do the heavy lifting for them.

The FormElement and ShowElement components are at the core of this work, the aim would be that new modules are built using this framework. It is important to note that the framework is not restrictive - it is possible to inject bespoke components directly into FormElement and ShowElement where there are particularly niche, we have introduced standardised components for rendering form elements (e.g. inputs, selects) and displaying data, Record Resources and Vendors) have been migrated to use it. A new suite of cypress tests has been written to verify the functionality as well as catch regressions and part of this is introducing component testing into Koha for any future Vue work that, as well as with an example SkeletonResource.vue to show how it should be used. There are also the live examples in the modules mentioned above.
jonathan.druart 2025-10-02 13:39:08 UTC Status Signed Off Passed QA
lucas 2025-10-02 16:25:53 UTC Status Passed QA Pushed to main
Keywords RM_priority
Version(s) released in 25.11.00
tomascohen 2025-10-02 17:59:32 UTC CC tomascohen

Back to bug 38201