Closed danielnixon closed 4 years ago
It's the strict mode
Type assertion, like a as string, a!,
a will be considered as uncovered Also, future minor release may introduce stricter type check in this mode, which may lower the type coverage rate
https://github.com/plantain-00/type-coverage#strict-mode
You can turn it off by removing --strict
you don't need it.
as const
should not count, I will fix it.
v2.8.1 should exclude as const
LGTM, thanks @plantain-00.
Version(if relevant): 2.8.0
Environment(if relevant):
Code(if relevant):
Expected:
Doesn't count as uncovered
Actual:
Is flagged as uncovered