Skip to content

📝 Add TypeDoc API reference parity for framework plugins - #4876

Draft
thomas-lebeau wants to merge 2 commits into
mainfrom
worktree-docs-plugin-parity
Draft

📝 Add TypeDoc API reference parity for framework plugins#4876
thomas-lebeau wants to merge 2 commits into
mainfrom
worktree-docs-plugin-parity

Conversation

@thomas-lebeau

Copy link
Copy Markdown
Collaborator

Motivation

The public TypeDoc API reference was inconsistent across framework integration packages — some plugins (Angular, Next.js, Nuxt, Vue, TanStack Router) lacked the same level of API documentation coverage as other packages.

Changes

  • Add typedoc.json entries for browser-rum-angular, browser-rum-nextjs, browser-rum-nuxt, browser-rum-vue, and the tanstack-router entry in browser-rum-react, so their public APIs are documented consistently.
  • Add missing exports/JSDoc where needed to support documentation generation (Next.js app/pages router, Nuxt error handling, Vue router integration).
  • Update docs/CONVENTIONS.md with guidance on TypeDoc parity across plugins.

Test instructions

  • Run yarn build and verify the TypeDoc site generates without errors for each affected package.
  • Spot-check the generated API reference pages for Angular, Next.js, Nuxt, Vue, and TanStack Router plugins to confirm the new entries render correctly.

Checklist

  • Tested locally
  • Tested on staging
  • Added unit tests for this change.
  • Added e2e/integration tests for this change.
  • Updated documentation and/or relevant AGENTS.md file

- Add typedoc.json for browser-rum-angular, browser-rum-nextjs and
  browser-rum-nuxt so TypeDoc reads src/entries/main.ts instead of
  silently falling back to the built cjs output
- Add JSDoc comments with @category Main/Error and @example blocks to
  the public exports of the nextjs, nuxt and vue plugin packages, and
  mark internal-only plugin types with @internal
- Export the NuxtApp type from browser-rum-nuxt's entry point so it's
  documented alongside NuxtPluginConfiguration
- Disable navigation.compactFolders in the root typedoc.json so
  single-member categories still render as real folders, and register
  additional highlightLanguages (bash, jsonc, tsx, vue, etc.) used in
  the new @example blocks
- Document this pattern in docs/CONVENTIONS.md so future packages
  follow the same setup
- Register packages/browser-rum-react/tanstack-router in typedoc.json entryPoints
- Export Merged, Combined, and ProfilerEventMap types so the public API surface referenced by the router package resolves correctly, with doc comments added where @inheritdoc could not resolve
@datadog-datadog-prod-us1

datadog-datadog-prod-us1 Bot commented Jul 14, 2026

Copy link
Copy Markdown

Pipelines  Tests

Fix all issues with BitsAI

⚠️ Warnings

🚦 1 Pipeline job failed

DataDog/browser-sdk | e2e: [chromium]   View in Datadog   GitLab

🧪 1 Test failed

salesforce views from salesforce/salesforceLwc.scenario.ts   View in Datadog
Test timeout of 30000ms exceeded.

[chromium] › salesforce/salesforceLwc.scenario.ts:26:11 › salesforce views ───────────────────────

    Test timeout of 30000ms exceeded.

    Error: page.evaluate: Target page, context or browser has been closed

       at ../lib/framework/waitForRequests.ts:15

...

ℹ️ Info

No other issues found (see more)

❄️ No new flaky tests detected

Useful? React with 👍 / 👎

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: a86e0d8 | Docs | Datadog PR Page | Give us feedback!

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