-
Notifications
You must be signed in to change notification settings - Fork 9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] chore: Introduce API Extractor and start generating documentation #5967
Conversation
@@ -22,7 +22,7 @@ import Protocol from './protocol'; | |||
import { Connection } from './Connection'; | |||
import { Page } from './Page'; | |||
import { ChildProcess } from 'child_process'; | |||
import type { Viewport } from './PuppeteerViewport'; | |||
import { Viewport } from './PuppeteerViewport'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API Extractor doesn't work fully with import type
yet so we should use regular imports. This isn't really an issue for us anyway.
customQueryHandlers, | ||
getQueryHandlerAndSelector, | ||
clearQueryHandlers, | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
didn't need these as well as the ESM exports
"module": "CommonJS" | ||
"module": "CommonJS", | ||
"declaration": true, | ||
"declarationMap": true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API Extractor works off the .d.ts
files so we need to generate them now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ack
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, and checking in new-docs
seems fine.
This PR introduces API Extractor to the codebase and generates new Markdown documentation into the
new-doc
folder. This documentation is incomplete and not meant to be used!This PR doesn't include the documentation in the
new-doc
folder in order to make this PR reviewable. If this lands, I will follow it up with another PR that generates the docs.Once this PR lands we can start slowly documenting our code (by converting the
api.md
docs into TSDoc comments) and once we think the new docs are ready we can make them the primary documentation and remove the old documentation.@mathiasbynens we could exclude
new-docs
from Git for now, but I think it's useful to see them rendered in pull requests when we begin work on improving them so I've left them in for now. LMK what you think.