github/puppeteer
0
0
Fork 0
mirror of https://github.com/puppeteer/puppeteer synced 2024-06-14 14:02:48 +00:00
Code Issues Packages Projects Releases Wiki Activity
96c3f943b2
puppeteer/utils/doclint
History
Alex Rudenko 06ba9632a4
fix: issue with reading versions.js in doclint (#7940) 
Partially reverts https://github.com/puppeteer/puppeteer/pull/7927
where the regression happened.
2022-01-28 12:01:12 +00:00
..
check_public_api chore: fix typings for ElementHandle.screenshot() options (#7602) 2021-09-29 15:46:57 +00:00
preprocessor chore: generate version range for deprecated versions (#7927) 2022-01-26 12:22:20 +01:00
.gitignore [doclint] move doclint testing to golden 2017-07-13 11:17:02 -07:00
cli.js fix: issue with reading versions.js in doclint (#7940) 2022-01-28 12:01:12 +00:00
Message.js docs: replace @return with @returns (#6006) 2020-06-12 12:38:24 +02: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