Conversation
f4eb248 to
64eb14f
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #3638 +/- ##
=======================================
Coverage 92.44% 92.44%
=======================================
Files 322 322
Lines 8129 8129
Branches 1838 1838
=======================================
Hits 7515 7515
Misses 614 614 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
64eb14f to
0ae4630
Compare
| on: | ||
| push: | ||
| branches: | ||
| - romanG/api-reference-github |
There was a problem hiding this comment.
Note : For testing purpose, will be deleted before pr get merged.
| url: 'https://datadoghq.dev' | ||
| baseurl: '/browser-sdk' | ||
|
|
||
| remote_theme: 'just-the-docs/just-the-docs' |
There was a problem hiding this comment.
Note : we may want to delete the left bar, working on a script to delete it after generation
| "woke": "scripts/cli woke" | ||
| "woke": "scripts/cli woke", | ||
| "build:types": "lerna run build:esm --stream", | ||
| "docs:api": "yarn build:types && api-extractor run --local -c packages/rum/api-extractor.json && api-extractor run --local -c packages/logs/api-extractor.json && api-extractor run --local -c packages/rum-slim/api-extractor.json && api-extractor run --local -c packages/rum-react/api-extractor.json && api-documenter markdown -i etc -o docs && node scripts/docs-jekyll.js", |
There was a problem hiding this comment.
💬 suggestion: Instead of inlining the conf for all packages here, you should use lerna to run the command. Something like
package.json=>- "docs:api:extractor": "lerna run docs:api"
- "docs:api": "yarn docs:api:extractor && api-documenter markdown -i etc -o docs && node scripts/docs-jekyll.js"
- for all packages (e.g.
rum-core/package.json):- "docs:api:extractor": "yarn build:esm && api-extractor run --local -c ./api-extractor.json"
There was a problem hiding this comment.
The api-extractor.json configuration is almost identical across packages. To avoid duplication, we could use extends.
|
closed in favor of #3677 |
Motivation
This PR introduces automated API reference generation for the Browser SDK using API generator. It addresses documentation inconsistencies by centralizing the public API surface, improving maintainability, and enabling integration into Datadog Docs or GitHub Pages.
Changes
See this web page to visit the api reference : https://datadoghq.dev/browser-sdk/
Test instructions
Use : docs:serve to test Jekyll locally
Checklist