thunderstrike/puppeteer
thunderstrike/puppeteer
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
21a722b3f8
puppeteer/utils/doclint
History
Andrey Lushnikov 67d109862a [doclint] parse getters as properties 
From the api standpoint, there's no difference between property
and a getter.

References #14.
2017-07-13 23:12:38 -07:00
..
test [doclint] parse getters as properties 2017-07-13 23:12:38 -07:00
.gitignore [doclint] move doclint testing to golden 2017-07-13 11:17:02 -07:00
Documentation.js [doclint] introduce class members 2017-07-13 23:02:43 -07:00
JSBuilder.js [doclint] parse getters as properties 2017-07-13 23:12:38 -07:00
lint.js [doclint] introduce class members 2017-07-13 23:02:43 -07:00
MDBuilder.js [doclint] introduce class members 2017-07-13 23:02:43 -07:00
README.md [doclint] Move doclint under utils/ 2017-07-13 00:28:52 -07: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
  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