Documentation comment not found for arrow function
getSiblingElement47 [ref]
48 );
49
50 const getSiblingElement = (list, property) => {51 const sibling = list.length > 0 ? list[0][property] : null;
52 return sibling instanceof HTMLElement ? sibling : null;
53 };Documentation comment not found for arrow function
handleScroll 7 useEffect(() => {
8 const containerElement = ref.current;
9
10 const handleScroll = () => {11 const rect = containerElement.getBoundingClientRect();
12 const visibleElements = Array.from(containerElement.children).filter((child) => {
13 const childRect = child.getBoundingClientRect();Documentation comment not found for function declaration
usePosition 1import { useCallback, useEffect, useState } from 'react';
2
3export function usePosition(ref) { 4 const [prevElement, setPrevElement] = useState(null);
5 const [nextElement, setNextElement] = useState(null);
6
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;
}