Documentation comments not found for functions and classes JS-D1001
Documentation
Minor
a month ago
—
a year old
Documentation comment not found for function declaration
dateDisable43 sel.attr('disabled', false);
44}
45
46function dateDisable(sel){47 sel.attr('disabled', 'disabled');
48}
Documentation comment not found for function declaration
dateEnable39 });
40}
41
42function dateEnable(sel){43 sel.attr('disabled', false);
44}
45Documentation comment not found for function declaration
processDateBoxes33 }
34}
35
36function processDateBoxes(dateCheckBox, dateSelects, dateSelects2){37 $(dateCheckBox).click(function(){
38 processDateInit(dateCheckBox, dateSelects, dateSelects2);
39 });Documentation comment not found for function declaration
processDateInit22 }
23}
24
25function processDateInit(dateCheckBox, dateSelects, dateSelects2){26 if ($(dateCheckBox).attr('checked')) {
27 dateEnable(dateSelects);
28 dateEnable(dateSelects2);Documentation comment not found for function declaration
processDateFields 1function processDateFields(){ 2 var dateFields = new Array();
3 var dateName;
4 var dateCheckBox;
Description
It is recommended to have documentation comments above, or right inside a function/class declaration. This helps developers, users and even the author understand the purpose of a code snippet or API function in the future.
NOTE: If you want to stop this issue from getting raised on certain constructs (arrow functions, class expressions, methods etc.), consider using the skipdoccoverage option under the analyzers.meta property in your .deepsource.toml file.
For example, the following configuration will silence this issue for class expressions and method definitions:
[analyzers.meta]
skip_doc_coverage = ["class-expression", "method-definition"]
Bad Practice
function sum(a, b) {
return a + b;
}
Recommended
/**
* Function to add two numbers
* @param a The first number to add
* @param b The second number to add
* @returns The sum of two numbers
*/
function sum(a, b) {
return a + b;
}