This repository has been archived by the owner on Oct 5, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 45
coverage stat tabulates uses rather than declarations #95
Labels
Comments
starpit
added a commit
to starpit/typewiz
that referenced
this issue
Apr 22, 2019
also emits a coverage report Fixes mockdeep#95
starpit
added a commit
to starpit/typewiz
that referenced
this issue
Apr 22, 2019
also emits a coverage report Fixes mockdeep#95
starpit
added a commit
to starpit/typewiz
that referenced
this issue
Apr 22, 2019
also emits a coverage report Fixes mockdeep#95
starpit
added a commit
to starpit/typewiz
that referenced
this issue
Apr 22, 2019
also emits a coverage report Fixes mockdeep#95
starpit
added a commit
to starpit/typewiz
that referenced
this issue
Apr 22, 2019
also emits a coverage report Fixes mockdeep#95
starpit
added a commit
to starpit/typewiz
that referenced
this issue
Apr 22, 2019
also emits a coverage report Fixes mockdeep#95
urish
added
component:core
enhancement
New feature or request
help wanted
Extra attention is needed
labels
Apr 23, 2019
Good call! Are you working on a PR? |
yes. i also am working on adding a coverage report. the report will break typecov down by declarations versus parameters versus returns i'm thinking of dropping identifiers altogether, as focusing on these is probably misleading; this will also increase the scalability of the tool, at least as far as the coverage report is concerned: e.g. in our code base (https://github.com/IBM/kui) there is a roughly 10x difference in magnitude between decls and identifiers. |
This sounds lovely, I'm looking forward to it. Once we have it, #94 will also make a lot more sense |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
the coverage utility is quite helpful. i notice that it increments the penalty for every use of an
any
variable. maybe this is working as designed, but i think it would be more helpful to penalizeany
variables once per declaration, rather than once per use?my thinking is that the magnitude of the fix is proportional to the number of declarations that need to be typed, rather than the number of such uses?
The text was updated successfully, but these errors were encountered: