History

jrandolf 80373f7a12 chore: use `composite` builds for tests (#8522 )		2022-06-15 12:05:25 +02:00
..
check_public_api	chore: use `composite` builds for tests (#8522 )	2022-06-15 12:05:25 +02:00
preprocessor	chore: use `curly` (#8519 )	2022-06-14 13:55:35 +02:00
.gitignore	[doclint] move doclint testing to golden	2017-07-13 11:17:02 -07:00
cli.js	chore: use `curly` (#8519 )	2022-06-14 13:55:35 +02:00
Message.js	chore: use exit code 0 for doclint file gen (#8377 )	2022-05-20 05:13:06 +00:00
README.md	chore: automate prettier in docs (#7014 )	2021-03-23 10:02:34 +01:00
Source.js	chore: use `curly` (#8519 )	2022-06-14 13:55:35 +02:00

DocLint

Doclint is a small program that lints Puppeteer's documentation against Puppeteer's source code.

Doclint works in a few steps:

Read sources in lib/ folder, parse AST trees and extract public API. Note that we run DocLint on the outputted JavaScript in lib/ rather than the source code in src/. We will do this until we have migrated src/ to be exclusively TypeScript and then we can update DocLint to support TypeScript.
Read sources in docs/ folder, render markdown to HTML, use puppeteer to traverse the HTML and extract described API.
Compare one API to another.

Doclint is also responsible for general markdown checks, most notably for the table of contents relevancy.

Running

npm run doc

Doclint has its own set of jasmine tests, located at utils/doclint/test folder.

To execute tests, run:

npm run test-doclint