Misha Kaletsky

idea: for `expiring-todo-comments`: warn when GitHub issue is closed

8

I think this idea has been raised before, but I'm not sure it has with this specific restriction: For a todo written like ```js // todo [#1234] until we refactor...

Rule proposal: `wrap-comments`

21

I spend too much of my life "balancing" jsdoc and `//` comments so they're roughly the same length as each other. The consequences of doing this/not doing this are: -...

PoC: SWC

7

Hi! Was going to write this as a comment but I thought a functional PR would be a nicer way to make a proposal. A cleaned up version of this...

Enhancement: [restrict-template-expressions] `allowURLSearchParams` option

2

### Before You File a Proposal Please Confirm You Have Done The Following... - [X] I have [searched for related issues](https://github.com/typescript-eslint/typescript-eslint/issues?q=is%3Aissue+label%3A%22enhancement%3A+plugin+rule+option%22) and found none that match my proposal. - [X]...

Add setFs to types

1

Adds the `setFs` method which exists in js to the typescript types.

no-restricted-disable - whitelist/blacklist based on error level

1

From [the docs for no-restricted-disable](https://github.com/mysticatea/eslint-plugin-eslint-comments/blob/b35ad0bfbff88440ec8506bfc77e3f6599820816/docs/rules/no-restricted-disable.md), it doesn't look like it's possible to do something like this: ``` { "eslint-comments/no-restricted-disable": ["warn", { "level": "error" }] } ``` This would allow disabling...

fix: make no-jest-import error message more accurate

2

It isn't quite accurate to say that Jest doesn't export anything. It exports the `run` and `runCLI` functions, even though it isn't generally recommended to use them ([yet](https://github.com/facebook/jest/issues/5048#issuecomment-470693540)). This updates...

**Describe the bug** ```js const x = await evaluate(() => { return document.querySelector('.doesNotExist').textContent }) ``` When no element with class `doesNotExist` exists `x` will have value `{}`. I think this...

Feature request: expose rules map in npm package

1

The way I'd like to use this is to upgrade a repo from JavaScript/eslint to TypeScript/tslint, but keeping as many as possible of my company's highly-customized eslint settings as possible....

disallow NaN for number types

3

How about an option to throw when `NaN` is assigned to a number type? Right now this library allows things like [`const x: number = parseFloat("hello");`](https://fabiandev.io/ts-runtime/#JTdCJTIyZWRpdG9yJTIyJTNBJTIyY29uc3QlMjB4JTNBJTIwbnVtYmVyJTIwJTNEJTIwcGFyc2VGbG9hdCglNUMlMjJoZWxsbyU1QyUyMiklM0IlNUNuJTIyJTJDJTIyb3B0aW9ucyUyMiUzQSU3QiUyMnRzck9wdGlvbnMlMjIlM0ElN0IlMjJmb3JjZSUyMiUzQXRydWUlMkMlMjJub0Fubm90YXRlJTIyJTNBZmFsc2UlMkMlMjJkZWNsYXJhdGlvblByZWZpeCUyMiUzQSUyMl8lMjIlN0QlMkMlMjJjb21waWxlck9wdGlvbnMlMjIlM0ElN0IlMjJub0ltcGxpY2l0QW55JTIyJTNBZmFsc2UlMkMlMjJzdHJpY3ROdWxsQ2hlY2tzJTIyJTNBdHJ1ZSUyQyUyMm5vSW1wbGljaXRSZXR1cm5zJTIyJTNBZmFsc2UlMkMlMjJub0ltcGxpY2l0VGhpcyUyMiUzQWZhbHNlJTJDJTIycmVtb3ZlQ29tbWVudHMlMjIlM0FmYWxzZSUyQyUyMmV4cGVyaW1lbnRhbERlY29yYXRvcnMlMjIlM0F0cnVlJTJDJTIyZW1pdERlY29yYXRvck1ldGFkYXRhJTIyJTNBZmFsc2UlMkMlMjJhbGxvd05vblRzRXh0ZW5zaW9ucyUyMiUzQXRydWUlMkMlMjJtb2R1bGUlMjIlM0E1JTJDJTIydGFyZ2V0JTIyJTNBMiU3RCUyQyUyMndpbmRvd09wdGlvbnMlMjIlM0ElN0IlMjJjb25zb2xlJTIyJTNBdHJ1ZSU3RCU3RCU3RA==) ...which makes sense as...