-
```warning Use object shorthand or index signatures instead of `Object`, e.g., `{[key: string]: string}` jsdoc/check-types``` is being applied to our JavaScript files. Either the example giv…
-
## Motivation
We have an [Nx](https://nx.dev/) monorepo where the public API for libraries are defined in a single file: `libs/path/to/lib/src/index.ts`.
The `publicOnly` option for the `js…
-
This is similar to https://github.com/gajus/eslint-plugin-jsdoc/issues/1124 but it's using `#` instead of TypeScript's `private`
## Expected behavior
When `jsdoc/require-jsdoc` is confi…
-
I would like to add a parser for ternary expressions -
```
expr ? expr : expr
```
The precedence of it is in the following file - https://github.com/nouritsu/rs-rcc/blob/main/src/parser.rs
It ha…
-
-
Implementing pratt parsing (or precedence climbing, which is supposedly [the same algorithm](https://www.oilshell.org/blog/2016/11/01.html)) could be useful. I quite like it for parsing mathematical e…
-
## Expected behavior
ESLint should report a "Missing JSDoc comment" rule violation for the first function as well as for the static class function.
## Actual behavior
It only reports the …
Pik-9 updated
9 months ago
-
## Expected behavior
No warning should be triggered when `this` param is accompanied by a destructured parameter.
## Actual behavior
A warning is triggered, implying that the `@pa…
-
Parsing expressions such as `1 + 2 * 3` is a common parsing example, there should be some code to show it in nom
Geal updated
12 months ago
-
I see there are some demand for reading jsdoc information, let's do this in two steps:
1. parse jsdoc into structured data, this should be lazy.
2. save them into trivias and have them accessible.…