Is playground necessary for coverage aggregation target?
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 195
- PR merge metrics
- No merged PRs in 30d
Description
Describe the feature
now coverage targets are
---------------------|---------|----------|---------|---------|-----------------------
File | % Stmts | % Branch | % Funcs | % Lines | Uncovered Line #s
---------------------|---------|----------|---------|---------|-----------------------
All files | 73.91 | 83.63 | 61.29 | 73.91 |
examples | 0 | 12.5 | 12.5 | 0 |
body.mjs | 0 | 0 | 0 | 0 | 1-11
error-handling.mjs | 0 | 0 | 0 | 0 | 1-13
first-request.mjs | 0 | 0 | 0 | 0 | 1-5
headers.mjs | 0 | 0 | 0 | 0 | 1-19
methods.mjs | 0 | 0 | 0 | 0 | 1-7
proxy.mjs | 0 | 0 | 0 | 0 | 1-9
query-string.mjs | 0 | 0 | 0 | 0 | 1-9
type-safety.ts | 0 | 100 | 100 | 0 | 2-21
playground | 0 | 0 | 0 | 0 |
index.mjs | 0 | 0 | 0 | 0 | 1-12
index.ts | 0 | 0 | 0 | 0 | 1-16
src | 87.55 | 88.38 | 85.71 | 87.55 |
base.ts | 100 | 100 | 100 | 100 |
error.ts | 95.91 | 85.71 | 100 | 95.91 | 13-14
fetch.ts | 98.01 | 94.25 | 87.5 | 98.01 | 238,270-273
index.ts | 0 | 0 | 0 | 0 | 1-35
node.ts | 37.5 | 25 | 0 | 37.5 | 14-35,39
types.ts | 0 | 0 | 0 | 0 |
utils.ts | 93.45 | 85.36 | 100 | 93.45 | 19-20,26-27,52-53,121
---------------------|---------|----------|---------|---------|-----------------------
but, Are examples and playground not necessary?
Additional information
- Would you be willing to help implement this feature?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the coverage configuration and command that produce the shown report, then inspect the examples and playground directories to determine whether they are intended test targets. Run coverage with those directories included and excluded, and confirm the chosen scope produces the expected report; document or configure the result so the target is intentional.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100