Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Automate & standardize package API docs #6119

JoshuaKGoldberg started this conversation in Technical Discussions
Discussion options

Right now packages have their own hand-written descriptions in their README.md files. in #5984 those are moved to mdx files to be shown on typescript-eslint.io. But they're still hand-written.

From @bradzacher's #5984 (comment):

Really we would want to use something like https://api-extractor.com/ to do some form of generation so that people have an in-depth reference of what's included.

Also some examples of how to use some things or why to use some things.

For example - people might not know why you'd use the TSESLint export from the package (it's because @types/eslint is built on top of the base @types/estree types which don't include our AST nodes).

Let's build off #5984's changes to add ... something! Investigation required.

You must be logged in to vote

Replies: 0 comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
1 participant
Morty Proxy This is a proxified and sanitized view of the page, visit original site.