-
## Expected behavior
The rule `jsdoc/require-returns` should require a `@returns` tag in a JSDoc comment for an async function that explicitly returns something.
## Actual behavior
…
-
Looks like tehre are some depenndencies between units.
Two examples:
```console
+ /usr/bin/pytest -ra
=========================================================================== test session start…
-
Manual instrumentation of branch coverage for the following functions.
This is done by writing to the file `data/branch-coverage` with `'a'` (append) flag enabled.
See structure in `tests/__init__.p…
-
# Description
Hi, while i'm using union type in JSDoc type definition, eslint is crashing :
```txt
ESLint stack trace:
[Error - 13:20:00] TypeError: Cannot read properties of undefined (readi…
-
## Expected behavior
This should be valid (it is called an index signature https://www.typescriptlang.org/docs/handbook/2/objects.html#index-signatures).
```js
/** @type {{[key: string]: string}}…
-
Having to explicitly choose the API endpoint, depending on the command type, is awkward. A new endpoint, that contained a built-in SQL parser, would be best. It would route the statements to the corre…
-
## Motivation
I want to restrict using `@type {{ foo: bar}}` and instead use `@typedef` comments with descriptions.
## Current behavior
Not implemented AFAIK.
## Desired behavior
A …
-
## Motivation
warn level rule will pass in lint-staged.
So, I want to turn all warn to error level in recommend config.
## Current behavior
The recommend rules all set to warn level: htt…
-
@rocky inspired a few thoughts I have about Mathics and what the team might consider for improvements to pattern matching and parsing and operator support.
# Pattern matching
My own project [Lor…
-
## Motivation
For beauty, can remove the extra useless space by auto fix.
I want to use this rule to replace https://github.com/hosseinmd/prettier-plugin-jsdoc.
## Current behavior
…