chore: enable eslint cache

[pkuczynski]

This significantly speeds up subsequent eslint runs

[ST-DDT]

This works really nice. Where does it store the cache if I want to delete it?

[pkuczynski]

This works really nice. Where does it store the cache if I want to delete it?

Root of the project. Its already gitignored.

[codecov]

Codecov Report

Merging #403 (3ca30ac) into main (bed7182) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #403   +/-   ##
=======================================
  Coverage   99.32%   99.32%           
=======================================
  Files        1920     1920           
  Lines      174272   174272           
  Branches      893      893           
=======================================
+ Hits       173099   173100    +1     
+ Misses       1117     1116    -1     
  Partials       56       56           

Impacted Files	Coverage Δ
src/helpers.ts	99.47% <0.00%> (+0.17%)	⬆️

[Shinigami92]

Tested it locally and seems to work
Just asking myself why this is not the default behavior of eslint 🤔
Should we also clean the cache-file on pnpm run clean?

[Shinigami92]

If we encounter any problems in the future, we can revert it

[Shinigami92]

@pkuczynski uhm... sry, but
How will this behave when having a dependency-update? Or something similar.
So e.g. the eslint rule itself changed in behavior but the file did not change?

So maybe we should really add it to the clean statement 😬

[ST-DDT]

Is it based on the content of the file itself?
What if you change the api in your method and that causes a warning in another (untouched) file?
( Is that even possible? 🤔 )

[pkuczynski]

I honestly never had a problem with that :) And I keep my dependencies up to date on a weekly basis. In the worse case scenario CI would caught the issue as it does not have the cache enabled

[Shinigami92]

In the worse case scenario CI would caught the issue as it does not have the cache enabled

Okay 👍

[Shinigami92]

We await approval from @prisis (or a third maintainer)
So give it some minutes