feat(eslint-plugin): add prefer-regexp-exec rule

[ldrick]

Fixes: #283

This PR adds a new rule: @typescript-eslint/prefer-regexp-exec.
I ended up with copying many things from #289, due to nearly the same problem is solved there already. Probably its useful to move getTypeName(type: ts.Type): string to utils - please let me know.

• This PR adds one dependency: eslint-utils. This is the same with feat(eslint-plugin): add prefer-string-starts-ends-with rule (fixes #285) #289 .

[codecov]

Codecov Report

Merging #305 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #305      +/-   ##
==========================================
+ Coverage    95.5%   95.52%   +0.02%     
==========================================
  Files          88       89       +1     
  Lines        4093     4112      +19     
  Branches     1150     1153       +3     
==========================================
+ Hits         3909     3928      +19     
  Misses         82       82              
  Partials      102      102

Impacted Files	Coverage Δ
...plugin/src/rules/prefer-string-starts-ends-with.ts	100% <100%> (ø)	⬆️
...ages/eslint-plugin/src/rules/prefer-regexp-exec.ts	100% <100%> (ø)
packages/eslint-plugin/src/util/types.ts	83.33% <100%> (+10%)	⬆️

[JamesHenry]

Nice, thanks @ldrick!

I think we'll merge @mysticatea's work first, and then we can see what is shared, so just putting a block on for now, but LGTM

[bradzacher]

Hi @ldrick - #289 has been merged, so if you update this PR, we can merge it un

[ldrick]

Hi @bradzacher , I am back from vacation and will change common used things. In the meanwhile, I have trouble with pulling master, due to 86 errors in linting. Did something change and how can this be fixed - because all of the linting issues refer not to this rule?

[bradzacher]

Try doing a yarn install followed by a build.

[ldrick]

Try doing a yarn install followed by a build.

I tried locally, but linting fails, with exactly the same as azure pipelines in this PR. 😭
Might it be an issue with fresh install? I checked out everything on a new notebook and ran yarn; yarn build so it should install everything from yarn.lock. Thank you

[bradzacher]

Ahh, I see what's happening.
For some reason you committed your config all.json branch into this branch (b6d7590).

Which is why there are so many extra files.
It also looks like an old version of the branch, because there are changes to recommended.json (which are no longer present in #313).

You'll have to go through and remove the changes to fix up the changeset in this branch.
I just checked out your branch and tested; if you remove the recommended.json changes, there are no lint errors.

[ldrick]

@bradzacher Wow, thank you many times, I literally screwed up my master and with it everything else. I'm going to round up this PR tomorrow and continue using only one notebook with my (kn)own configuration. 🙇

[ldrick]

I did everything, I wanted to do. Please check, if moving getTypeName is what everyone would have expected and the way it should be. Thanks 👍

stale

[ldrick]

Hi, it would be nice to merge this one, to save me from merging masters 😸 and it was already approved. Thanks

[bradzacher]

@ldrick - We try to leave PRs open for around 2-3 weeks after getting an approval because we like to have 2 review approvals per feature PR.
We do 2-3 weeks because not all the core maintainers are available to spend a few hours every week.

Don't worry about checking back and merging master regularly. We'll coordinate that when it comes time to merge it.

That being said, it's probably time to merge this one in once these checks finish!