Repo: Add unit tests inside type-utils #8358
Labels
accepting prs
Go ahead, send a pull request that resolves this issue
locked due to age
Please open a new issue if you'd like to say more. See https://typescript-eslint.io/contributing.
package: type-utils
Issues related to the @typescript-eslint/type-utils package
repo maintenance
things to do with maintenance of the repo, and not with code/docs
tests
anything to do with testing
Comments
3 tasks
3 tasks
3 tasks
3 tasks
3 tasks
3 tasks
3 tasks
|
Status update: coverage is at ~62.44% now per https://app.codecov.io/gh/typescript-eslint/typescript-eslint/commit/5d9f49c62735e05fde53e1d4ac651218938769b7/tree/packages/type-utils. Nice! Shoutout @y-hsgw for sending a bunch of PRs. 🎉 |
3 tasks
This was referenced Sep 29, 2024
|
I think we can consider this closed for now. We're getting to the point of remaining functions not being super valuable. Thanks for the PRs, everyone! If there are individual functions anybody thinks should be tested, I'd suggest filing an individual repo tooling issue with why. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Suggestion
packages/type-utilsprovides a suite of types/TypeScript-related functions. They're used in many rules. But because we don't merge coverage reports across packages (#6701), it shows up as having surprisingly low unit test coverage. E.g.builtinSymbolLikes.tson 1d7447f right now has 0%. https://app.codecov.io/gh/typescript-eslint/typescript-eslint/blob/1d7447f4fd5e2fbae4211eb5fc07e93cf570b6b3/packages%2Ftype-utils%2Fsrc%2FbuiltinSymbolLikes.tsThe text was updated successfully, but these errors were encountered: