Skip to content

docs: generate the API reference with TypeDoc - #11

Merged
mfazekas merged 2 commits into
mainfrom
docs/typedoc
Oct 22, 2026
Merged

mfazekas merged 2 commits into
mainfrom
docs/typedoc

Conversation

@mfazekas

@mfazekas mfazekas commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

Generates the API reference from the JSDoc in src/ with TypeDoc and typedoc-plugin-markdown. scripts/typedoc-docusaurus.mjs shapes the output for docs/navigation/api/ in rnmapbox/maps-docs: frontmatter with an edit link to the source, a "generated, don't edit" comment, and sidebar categories per @group (Core, Components, Routes, Events). yarn docs writes to docs/api/ (gitignored), and CI runs it with warnings as errors so broken {@link}s fail.

.github/workflows/update-docs.yml runs on release: published (or manually with a ref), generates from the tag and pushes to maps-docs. It needs a MAPS_DOCS_DEPLOY_KEY secret with write access to rnmapbox/maps-docs.

Also fills in thin JSDoc, and fixes the README: the package is on npm as @rnmapbox/navigation@next, and why @rnmapbox/maps >= 10.3.11 is required.

The generated site for alpha.1 is in rnmapbox/maps-docs#14.

Add TypeDoc with typedoc-plugin-markdown and a small local plugin that
shapes the output for docs/navigation/api in rnmapbox/maps-docs
(frontmatter, sidebar categories, MDX-safe). `yarn docs` writes it to
docs/api; CI runs it with warnings as errors. update-docs.yml regenerates
it from each published release and pushes it to maps-docs.

Fill in the JSDoc the reference is built from, and update the README now
that the package is on npm under `next`.
Docusaurus treats Navigation/Navigation.md as the category's index page.
@mfazekas
mfazekas merged commit be47913 into main Oct 22, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant