Summary: | We should use JSDoc | ||
---|---|---|---|
Product: | Koha | Reporter: | Tomás Cohen Arazi (tcohen) <tomascohen> |
Component: | ERM | Assignee: | Jonathan Druart <jonathan.druart> |
Status: | NEW --- | QA Contact: | |
Severity: | enhancement | ||
Priority: | P5 - low | CC: | jonathan.druart, jonathan.field, martin.renvoize, matt.blenkinsop, paul.derscheid, pedro.amorim |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
Change sponsored?: | --- | Patch complexity: | --- |
Documentation contact: | Documentation submission: | ||
Text to go in the release notes: | Version(s) released in: | ||
Circulation function: |
Description
Tomás Cohen Arazi (tcohen)
2024-04-01 17:49:14 UTC
+1 Agreed. Adding tests for our JS functions would also be great (looking at you staff-global.js) I thought we already had a coding guideline for this but I'm not seeing it. I completely agree, we should require is and catch missing cases with the QA scripts if we can. +1 to JSDoc and totally agree on qa-script integration. VSCod{e,ium} even generates the base for JSDoc automatically, so it's not really much additional work. Who/Where/When? To add to the dev meeting agenda? Yes, let's add it. |