Generate object reference docs - #3286
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Okay, have pushed a minor docs review - clerk-options after reviewing the Typedoc output of the
Will continue reviewing and push a second docs review with the rest. |
|
@alexisintech Here is a second docs review pt 2 to just add the Typedoc outputs for the intros of each object. Noticed they were there, looked good, but weren't being used. Again, if you don't love it, feel free to revert. This is in conjunction with the docs review in |
me personally, I liked having the intro text in the mdx but your way of using typedoc for the intro text is fine too. I prefer the first way because if we ever want to update copy, we don't have to rely on a |
@alexisintech Yeah that's very fair feedback. Reverted changes: Revert 2nd docs review. |
… public-user-data intro Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
Pushed some changes directly in fb691ec.
LMK if these look good to you. Leaveing a few comments for things I felt less confident on. |
Co-authored-by: Michael Novotny <manovotny@gmail.com>
Co-authored-by: Alexis Aguilar <98043211+alexisintech@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Michael Novotny <manovotny@gmail.com> Co-authored-by: Sarah Soutoul <sarah@clerk.dev> Co-authored-by: Nicolas Angelo <nick.angelo.scott@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
|
This PR modifies files in the 'clerk-typedoc/' folder. These files are auto-generated from the clerk/javascript repository and should not be edited directly. To make changes to TypeDoc documentation:
Thanks for contributing! 🙏 |
|
waiting on docs(shared): Fix Typedoc links to get merged |
Co-authored-by: Alexis Aguilar <98043211+alexisintech@users.noreply.github.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Michael Novotny <manovotny@gmail.com> Co-authored-by: Sarah Soutoul <sarah@clerk.dev> Co-authored-by: Nicolas Angelo <nick.angelo.scott@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Pushed a small follow-up in b3803bb.
LMK if this looks good to you. Posting one more question. |
| | <a id="issignedin"></a> `isSignedIn` | `boolean` | Indicates whether the current user has a valid signed-in client session. | | ||
| | <a id="isstandardbrowser"></a> `isStandardBrowser` | <code>undefined \| boolean</code> | Indicates whether the instance is being loaded in a standard browser environment. Set to `false` on native platforms where cookies cannot be set. When `undefined`, Clerk assumes a standard browser. | | ||
| | <a id="loaded"></a> `loaded` | `boolean` | Indicates whether the `Clerk` object is ready for use. Set to `false` when the `status` is `"loading"`. Set to `true` when the `status` is `"ready"` or `"degraded"`. | | ||
| | <a id="oauthapplication"></a> `oauthApplication` | [`OAuthApplicationNamespace`](../o-auth-application-namespace.mdx) | OAuth application helpers (e.g. consent metadata for custom consent UIs). | |
There was a problem hiding this comment.
The oauthApplication row renders as [OAuthApplicationNamespace](../o-auth-application-namespace.mdx) — a raw relative .mdx path that leaks into all 11 SDK-scoped rendered clerk.mdx pages (its table siblings organization/session/user resolve to real /docs/... routes via SDKLink).
Root cause is upstream: o-auth-application-namespace isn't in LINK_REPLACEMENTS in clerk/javascript's .typedoc/custom-plugin.mjs (siblings like o-auth-consent-info and organization-resource are).
Heads up that build:tsx doesn't catch this — the link validator skips relative .mdx links inside embedded Typedoc tables, so the clean build isn't proof here.
Fix would be adding the mapping there + likely a routed docs/reference/types/oauth-application-namespace.mdx page (parallel to the image-resource page this PR adds), then regenerate. Worth a ticket like the others?
There was a problem hiding this comment.
yes we can update this as a followup based on this PR: https://github.com/clerk/clerk-docs/pull/3315/changes#diff-4758545ec3ecda5309aeef6572743a8c3613c42b0f0e40128f2a93a6eb4c9bbc
if we update the link now, there's nothing to point it to because the oauth stuff doesn't exist yet.
I've created a ticket https://linear.app/clerk/issue/DOCS-11827/typedoc-oauthapplicationnamespace-needs-a-replacement

To test:
pnpm run typedoc:generate:skip-build(as long as you haveclerk-docsandclerk/javascriptsymlinked; see theclerk/clerk README.md)clerk/clerk, runpnpm run dev)What does this solve? What changed?
It's time to get our
/objectsreference docs generated using typedoc!Related resources
clerk/javascriptPRhttps://linear.app/clerk/issue/DOCS-11789/generate-objects-docs