Type errors in anagram tests when strict mode is enabled #1594
Description
In the provided Jest tests for the anagram exercise, several expected arrays are declared empty without an explicit type annotation.
When the TypeScript compiler is run with "strict": true (as it is in the default Exercism TypeScript tsconfig), noImplicitAny is also enabled by default. This causes TypeScript compilation errors for these untyped empty arrays.
Steps to Reproduce
- Download the anagram exercise for the TypeScript track.
- Install dependencies:
yarn install- Run test:
yarn test`Actual Behavior:
Typescript reports errors like
anagram.test.ts:66:11 - error TS7034: Variable 'expected' implicitly has type 'any[]' in some locations where its type cannot be determined.Expected Behavior
The tests should compile successfully under the default configuration without requiring learners to change type annotations locally.
Proposed Fix
Add explicit type annotations for all empty expected arrays. For example:
- const expected = []
+ const expected: string[] = [] Why this helps
- Keeps the tests type-safe while still compiling with "strict": true.
- Prevents learners from hitting compiler errors unrelated to the exercise logic.
- Makes the learning experience smoother without weakening the strictness settings.
- I would be happy to open a pull request with the fix if that would be helpful.