-
After trying to upgrade `eslint-plugin-jsdoc` to the latest version 37.9.2, our CI started failing with an ESLint error.
Change: https://bitbucket.org/atlassian/atlassian-browser-devtools/pull-reque…
macku updated
2 years ago
-
## Motivation
TypeScript Do's and Dont's (https://www.typescriptlang.org/docs/handbook/declaration-files/do-s-and-don-ts.html#general-types) says to never use `Object` (capital O). So when in types…
-
See some discussions here https://github.com/npm/npm/issues/8773
## Expected behavior
```ts
// code.js
/**
* @license
* Copyright 2022 Acme, Corp. All Rights Reserved.
*/
…
-
Currently all field references are parsed in one go, with the `.` have the highest binding power of any operator
This means something like
```
let x: Struct;
...
let x_ptr = &x;
*x.field = 7;
`…
-
## Motivation
## Current behavior
Using TypeScript built-in globals such `ReturnType` brings errors from the `no-undefined-types` rule.
## Desired behavior
Include these by default…
-
Getting error:
```
Syntax error in type: String eslint jsdoc/valid-types
Syntax error in namepath: value eslint jsdoc/valid-types
```
Uppercase String is not working
```js
/**
…
fab1o updated
2 years ago
-
## The issue
As I started adding the comma operator (` , `), I ran into an issue: _operator precedence_.
My current understanding is that this issue exists when a language has more than one infix …
-
* **Description**
I'm building python binding; pyoperon from source with this install
example. [link](https://operongp.readthedocs.io/en/latest/build.html#linux-conda). After several partially s…
-
## Expected behavior
`check-tag-names` should not warn on valid tag `@internal`
```js
/**
* @internal
*/
```
## Actual behavior
> Invalid JSDoc tag name "internal". eslint [jsd…
-
## Motivation
Using the `require-jsdoc` rule, we currently have no way of excluding "trivial" methods, so we have to write many comments that just paraphrase the method name. In Java-Checkstyle…