thunderstrike/puppeteer
thunderstrike/puppeteer
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
dac3e65533
puppeteer/utils/doclint
History
Randolf Jung bc1326f16e chore: build main docs after publishing
2022-05-31 15:38:34 +02:00
..
check_public_api feat: add back and forward mouse buttons (#8284) 2022-04-27 21:00:07 +00:00
preprocessor fix: process documentation during publishing (#8433) 2022-05-30 21:50:34 +02:00
.gitignore [doclint] move doclint testing to golden 2017-07-13 11:17:02 -07:00
cli.js chore: build main docs after publishing 2022-05-31 15:38:34 +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 docs: replace @return with @returns (#6006) 2020-06-12 12:38:24 +02:00

README.md

DocLint

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

Doclint works in a few steps:

  1. 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.
  2. Read sources in docs/ folder, render markdown to HTML, use puppeteer to traverse the HTML and extract described API.
  3. 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

Tests

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

To execute tests, run:

npm run test-doclint