Ori Livni

Don't allow `resultFn` to resolve to implicit any params

2

I saw this trick in React 18 types: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/56210/files#diff-32cfd8cb197872bcba371f5018185d2e75fa540b52cda2dd7d8ac12dcc021299R1068 And the discussion https://github.com/DefinitelyTyped/DefinitelyTyped/issues/52873#issuecomment-845806435 I think we should ban implicit any as well. The only issue is that it might be...

using --- automatically trigger yaml syntax even if there was no ` or ```yaml

2

``` normal text here --- everything here is a yaml syntax ``` it's a problem because `---` is used as a separator. by the way, thanks! this project makes markdown...

Types issue with having `(RuleSetRule | "...")` instead of `RuleSetRule`

1

# Bug report **What is the current behavior?** Wrong type of `(RuleSetRule | "...")` repeated in a few places in `types.d.ts` **If the current behavior is a bug, please provide...

The project might introduce XSS

2

## 🐛 Bug Report SVGR doesn't seems to contain any option to sanitize SVGs  ## To Reproduce Just add `` with the wanted XSS...

moving to ESLint

2

ESLint supports parses like babel-parser, that allow better testing (style / linting errors). especially because decorators are experimental, it's a pain to run JSCS / JSHint tests