fix(types): locale proxy

[ST-DDT]

The main sources don't show the error, but the test code does:

(e.g. date.spec.ts)

[ST-DDT]

I'm not sure whether this is the correct solution.

[codecov]

Codecov Report

Merging #2099 (31aede5) into next (8395e69) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##             next    #2099      +/-   ##
==========================================
- Coverage   99.59%   99.59%   -0.01%     
==========================================
  Files        2567     2567              
  Lines      243368   243371       +3     
  Branches     1253     1247       -6     
==========================================
- Hits       242394   242380      -14     
- Misses        947      964      +17     
  Partials       27       27              

Impacted Files	Coverage Δ
src/locale-proxy.ts	100.00% <100.00%> (ø)
src/modules/helpers/index.ts	99.07% <100.00%> (-0.01%)	⬇️
src/modules/word/filterWordListByLength.ts	100.00% <100.00%> (ø)

... and 2 files with indirect coverage changes

[xDivisionByZerox]

The main sources don't show the error, but the test code does [...]

I'm pretty sure that is because the test files are not concluded in the tsconfig.json. I don't actually know which config files they use, but they seem to have different TS config settings. If you include 'test/**/*' in the tsconfig.json file the error is gone.

If you then activate the strictNullChecks rule, the error is there again and additionally in the source files. So we essentially missing strict configuration settings.

[Shinigami92]

I checked if we could use any instead of unknown, but then we are affected by not being refactor safe 😕
So if someone really uses the for custom definitions, they are forced to cast 🤷

[xDivisionByZerox]

We may want to start adding TS compile tests to the project. Just an idea.

[Shinigami92]

We may want to start adding TS compile tests to the project. Just an idea.

No, we just need to start using strict
see my already started efforts at

• infra: reduce tsconfig complexity #2102

we dont need tests, we need more safe checked TS itself