Documentation coverage?

Open
#356 1 comment 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
documentation

Research direction

The issue does not name a file, test, or entry point. Start by reviewing the repository documentation and determine whether TSDoc provides or recommends a documentation-coverage tool; done would be a documented answer or a clearly scoped follow-up change.

Written by the indexing model from the issue text.

Description

Hello,

I'm trying to track which parts of a codebase need some more documentation.

Is there a tool for this somewhere I wonder?

Dominant language
TypeScript
Stars
5k
Forks
162
Avg merge
17h 24m
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/tsdoc

All issues in microsoft/tsdoc

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.