Skip to content

Conversation

@SarahSoutoul
Copy link
Contributor

@SarahSoutoul SarahSoutoul commented Nov 18, 2025

Description

Context: clerk/clerk-docs#2649 (comment)

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Chores
    • Added changeset tracking configuration
    • Cleaned up internal documentation comments

@SarahSoutoul SarahSoutoul self-assigned this Nov 18, 2025
@changeset-bot
Copy link

changeset-bot bot commented Nov 18, 2025

🦋 Changeset detected

Latest commit: 6420482

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@vercel
Copy link

vercel bot commented Nov 18, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
clerk-js-sandbox Ready Ready Preview Comment Nov 18, 2025 5:08pm

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 18, 2025

Walkthrough

A changeset file placeholder was added to the repository. A documentation comment block was removed from the ClerkAPIResponseError class without modifying the class implementation or behavior.

Changes

Cohort / File(s) Summary
Changeset metadata
.changeset/green-roses-decide.md
Added empty changeset placeholder file with front matter block
Error handling documentation
packages/shared/src/errors/clerkApiResponseError.ts
Removed documentation comment preceding the ClerkAPIResponseError class; no implementation changes

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Verify the intent behind removing the documentation comment—ensure important context wasn't accidentally lost
  • Confirm the changeset file placeholder is intentional and properly configured

Poem

🐰 A comment takes flight, swept away clean,
While changesets rest in their quiet routine.
Less docs, less noise, a simpler sight,
The codebase hops lighter into the night!

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title references fixing a 'typedoc error' but the actual changes remove a documentation comment and add an empty changeset file, which don't clearly address a typedoc link error. Clarify the title to better reflect the actual changes, such as 'fix(shared): Remove typedoc comment from ClerkAPIResponseError' or provide more context about what typedoc error is being fixed.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch ss/fix-link-typedoc

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@SarahSoutoul SarahSoutoul changed the title Fix link typedoc error fix(shared): Fix link typedoc error Nov 18, 2025
/**
* Class representing a Clerk API Response Error.
*/
export class ClerkAPIResponseError extends ClerkError implements ClerkAPIResponseErrorInterface {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you specifically not want this class to be included in the typedoc output?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes. It's already being outputted, so there was a duplication. This comment was added as part of my work, but realized it caused the duplication.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are two ClerkAPIResponseError. @NWylynko

Screenshot 2025-11-18 at 11 00 27 am Screenshot 2025-11-18 at 11 00 19 am

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 66fdeb4 and 14da6d9.

📒 Files selected for processing (2)
  • .changeset/green-roses-decide.md (1 hunks)
  • packages/shared/src/errors/clerkApiResponseError.ts (0 hunks)
💤 Files with no reviewable changes (1)
  • packages/shared/src/errors/clerkApiResponseError.ts
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: Analyze (javascript-typescript)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (2)
.changeset/green-roses-decide.md (2)

1-2: Request visibility into the ClerkAPIResponseError documentation change.

The AI summary indicates that a documentation comment block was removed from the ClerkAPIResponseError class in packages/shared/src/errors/clerkApiResponseError.ts, but that file was not provided for review. The PR title mentions a "link typedoc error" fix.

Please verify:

  1. What specific JSDoc comment or link was causing the typedoc error?
  2. Why was the entire documentation block removed rather than fixing the problematic link?
  3. Are there any side effects to removing documentation from this error class?

1-2: PR submission is incomplete.

The PR checklist items (pnpm test, pnpm build, JSDoc updates, documentation) are not marked as completed. Before merging, please ensure:

  • Changes have been tested locally
  • Build succeeds with pnpm build
  • All JSDoc/documentation is accurate given the changes
  • Any affected documentation is updated

Comment on lines +1 to +2
---
---
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Changeset file is incomplete and will fail validation.

The changeset file must declare which package(s) were changed and the bump type (patch/minor/major) between the --- delimiters. The current file contains only empty delimiters.

Based on the PR title mentioning "fix(shared)", the changeset should declare the @clerk/shared package.

Apply this diff to add the required package declaration:

 ---
---
+@clerk/shared: patch
+"Fix link typedoc error"
+---

Note: Replace patch with minor or major if appropriate for your versioning strategy.

Committable suggestion skipped: line range outside the PR's diff.

🤖 Prompt for AI Agents
In .changeset/green-roses-decide.md around lines 1 to 2, the changeset is empty
and will fail validation; update the section between the '---' delimiters to
declare the changed package and bump type by adding an entry for @clerk/shared
with the desired release level (e.g., patch), for example replace the empty
content with a YAML block listing the package name and "patch" (or
"minor"/"major" if appropriate) so the file contains the required package
declaration and version bump type.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 18, 2025

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@7251

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@7251

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@7251

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@7251

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@7251

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@7251

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@7251

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@7251

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@7251

@clerk/express

npm i https://pkg.pr.new/@clerk/express@7251

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@7251

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@7251

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@7251

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@7251

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@7251

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@7251

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@7251

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@7251

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@7251

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@7251

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@7251

@clerk/types

npm i https://pkg.pr.new/@clerk/types@7251

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@7251

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@7251

commit: 6420482

@wobsoriano wobsoriano merged commit 1d7af3e into main Nov 18, 2025
42 of 43 checks passed
@wobsoriano wobsoriano deleted the ss/fix-link-typedoc branch November 18, 2025 17:26
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.

4 participants