multiClose
3741 })();
3742 };
3743
3744 var multiClose = function(thisRef, options) {3745
3746 var self = thisRef;
3747 var html = '<a href="javascript:void(0)" class="' + options.className + '" tabindex="-1" title="' + escape_html(options.title) + '">' + options.label + '</a>';
singleClose
3695 append : true
3696 }, options);
3697
3698 var singleClose = function(thisRef, options) {3699
3700 options.className = 'remove-single';
3701
equalizeSizes
3653 return width;
3654 };
3655
3656 var equalizeSizes = function() {3657 var i, n, height_max, width, width_last, width_parent, $optgroups;
3658
3659 $optgroups = $('[data-group]', self.$dropdown_content);
getScrollbarWidth
3637 };
3638 })();
3639
3640 var getScrollbarWidth = function() {3641 var div;
3642 var width = getScrollbarWidth.width;
3643 var doc = document;
addGroup
3443 }
3444 };
3445
3446 var addGroup = function($optgroup) {3447 var i, n, id, optgroup, $options;
3448
3449 $optgroup = $($optgroup);
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"]
function sum(a, b) {
return a + b;
}
/**
* 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;
}