Skip to content

chore(clerk-js,localizations): Deprecate Personal Account semantics with Personal Workspace #6402

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

LauraBeatris
Copy link
Member

@LauraBeatris LauraBeatris commented Jul 26, 2025

Description

Context

We're launching after-auth soon, and aim to get our product aligned with the nomenclature for accounts that aren't tied to orgs.

Our Docs & Dashboard are being updated to mention "Personal Workspace" and therefore the SDK needs to be consistent with it as well.

Changes

  • Update English localization of organizationSwitcher['personalWorkspace'] to Personal account
  • Update JSDocs for hidePersonal prop
  • Deprecate expectPersonalAccount in favor of expectPersonalWorkspace

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

Summary by CodeRabbit

  • Style

    • Updated all user-facing references from "personal account" to "personal workspace" across the UI and localization strings for improved consistency.
  • Documentation

    • Revised documentation and comments to reflect the terminology change from "personal account" to "personal workspace."
    • Added deprecation notice for expectPersonalAccount in favor of expectPersonalWorkspace in testing documentation.
  • Tests

    • Updated test descriptions and assertions to use "personal workspace" instead of "personal account."
    • Added new test utility method for "personal workspace" and marked the old one as deprecated.

Copy link

vercel bot commented Jul 26, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
clerk-js-sandbox ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 27, 2025 2:11pm

Copy link

changeset-bot bot commented Jul 26, 2025

🦋 Changeset detected

Latest commit: f5606a6

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

This PR includes changesets to release 22 packages
Name Type
@clerk/localizations Patch
@clerk/clerk-js Patch
@clerk/types Patch
@clerk/testing Minor
@clerk/clerk-react Patch
@clerk/chrome-extension Patch
@clerk/clerk-expo Patch
@clerk/agent-toolkit Patch
@clerk/astro Patch
@clerk/backend Patch
@clerk/elements Patch
@clerk/expo-passkeys Patch
@clerk/express Patch
@clerk/fastify Patch
@clerk/nextjs Patch
@clerk/nuxt Patch
@clerk/react-router Patch
@clerk/remix Patch
@clerk/shared Patch
@clerk/tanstack-react-start Patch
@clerk/themes Patch
@clerk/vue Patch

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

Copy link
Contributor

coderabbitai bot commented Jul 26, 2025

📝 Walkthrough

Walkthrough

This change set standardizes terminology across the codebase, replacing references to "personal account" with "personal workspace" in UI text, localization strings, test descriptions, and documentation comments. Updates span application components, test suites, localization files, and type documentation. In the testing utilities, a new method expectPersonalWorkspace is introduced to supersede the now-deprecated expectPersonalAccount, both of which match either term for backward compatibility. Several changeset files document these updates, including deprecation notices and patch releases for relevant packages. No functional logic or control flow is altered.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Complexity label: Simple
Rationale:
The changes are primarily search-and-replace terminology updates, with minimal impact on logic or structure. The introduction and deprecation of a testing utility method adds slight complexity, but overall, the review is straightforward and limited in scope.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9333d5d and 7cda61e.

📒 Files selected for processing (5)
  • .changeset/petite-books-care.md (1 hunks)
  • .changeset/red-horses-worry.md (1 hunks)
  • .changeset/thin-days-dress.md (1 hunks)
  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx (6 hunks)
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx (4 hunks)
✅ Files skipped from review due to trivial changes (2)
  • packages/clerk-js/src/ui/components/OrganizationList/tests/OrganizationList.test.tsx
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/tests/OrganizationSwitcher.test.tsx
🚧 Files skipped from review as they are similar to previous changes (3)
  • .changeset/petite-books-care.md
  • .changeset/thin-days-dress.md
  • .changeset/red-horses-worry.md
⏰ 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). (5)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Formatting | Dedupe | Changeset
  • GitHub Check: Build Packages
  • GitHub Check: semgrep/ci
  • GitHub Check: Analyze (javascript-typescript)

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

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: 0

🧹 Nitpick comments (2)
packages/localizations/src/en-GB.ts (1)

471-478: Confirm intended capitalization of “workspace”.

The PR description states the new terminology is “Personal Workspace” (capital W), but the localized value is "Personal workspace" (lower-case w).
Please double-check the product copy guide for title-case vs sentence-case and align accordingly across all locales to avoid UI inconsistency.

packages/localizations/src/en-US.ts (1)

465-472: Verify consistency with en-GB and Docs.

Same capitalization question as in en-GB: the string is "Personal workspace" while the PR objective cites “Personal Workspace”.
Ensure both locales – and any other that were updated – use the approved casing.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0452a0e and 8655210.

📒 Files selected for processing (8)
  • integration/templates/next-app-router/src/app/personal-account/page.tsx (1 hunks)
  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx (7 hunks)
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx (5 hunks)
  • packages/localizations/src/en-GB.ts (1 hunks)
  • packages/localizations/src/en-US.ts (1 hunks)
  • packages/localizations/src/utils/enUS_v4.ts (1 hunks)
  • packages/testing/src/playwright/unstable/page-objects/organizationSwitcher.ts (1 hunks)
  • packages/types/src/clerk.ts (2 hunks)
🧰 Additional context used
📓 Path-based instructions (18)
**/*.{js,jsx,ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

**/*.{js,jsx,ts,tsx}: All code must pass ESLint checks with the project's configuration
Follow established naming conventions (PascalCase for components, camelCase for variables)
Maintain comprehensive JSDoc comments for public APIs
Use dynamic imports for optional features
All public APIs must be documented with JSDoc
Provide meaningful error messages to developers
Include error recovery suggestions where applicable
Log errors appropriately for debugging
Lazy load components and features when possible
Implement proper caching strategies
Use efficient data structures and algorithms
Profile and optimize critical paths
Validate all inputs and sanitize outputs
Implement proper logging with different levels

Files:

  • packages/localizations/src/utils/enUS_v4.ts
  • packages/localizations/src/en-US.ts
  • packages/localizations/src/en-GB.ts
  • integration/templates/next-app-router/src/app/personal-account/page.tsx
  • packages/types/src/clerk.ts
  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/testing/src/playwright/unstable/page-objects/organizationSwitcher.ts
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Use Prettier for consistent code formatting

Files:

  • packages/localizations/src/utils/enUS_v4.ts
  • packages/localizations/src/en-US.ts
  • packages/localizations/src/en-GB.ts
  • integration/templates/next-app-router/src/app/personal-account/page.tsx
  • packages/types/src/clerk.ts
  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/testing/src/playwright/unstable/page-objects/organizationSwitcher.ts
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
packages/**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

TypeScript is required for all packages

Files:

  • packages/localizations/src/utils/enUS_v4.ts
  • packages/localizations/src/en-US.ts
  • packages/localizations/src/en-GB.ts
  • packages/types/src/clerk.ts
  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/testing/src/playwright/unstable/page-objects/organizationSwitcher.ts
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
packages/**/*.{ts,tsx,d.ts}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Packages should export TypeScript types alongside runtime code

Files:

  • packages/localizations/src/utils/enUS_v4.ts
  • packages/localizations/src/en-US.ts
  • packages/localizations/src/en-GB.ts
  • packages/types/src/clerk.ts
  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/testing/src/playwright/unstable/page-objects/organizationSwitcher.ts
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

Use proper TypeScript error types

**/*.{ts,tsx}: Always define explicit return types for functions, especially public APIs
Use proper type annotations for variables and parameters where inference isn't clear
Avoid any type - prefer unknown when type is uncertain, then narrow with type guards
Use interface for object shapes that might be extended
Use type for unions, primitives, and computed types
Prefer readonly properties for immutable data structures
Use private for internal implementation details
Use protected for inheritance hierarchies
Use public explicitly for clarity in public APIs
Prefer readonly for properties that shouldn't change after construction
Prefer composition and interfaces over deep inheritance chains
Use mixins for shared behavior across unrelated classes
Implement dependency injection for loose coupling
Let TypeScript infer when types are obvious
Use const assertions for literal types: as const
Use satisfies operator for type checking without widening
Use mapped types for transforming object types
Use conditional types for type-level logic
Leverage template literal types for string manipulation
Use ES6 imports/exports consistently
Use default exports sparingly, prefer named exports
Use type-only imports: import type { ... } from ...
No any types without justification
Proper error handling with typed errors
Consistent use of readonly for immutable data
Proper generic constraints
No unused type parameters
Proper use of utility types instead of manual type construction
Type-only imports where possible
Proper tree-shaking friendly exports
No circular dependencies
Efficient type computations (avoid deep recursion)

Files:

  • packages/localizations/src/utils/enUS_v4.ts
  • packages/localizations/src/en-US.ts
  • packages/localizations/src/en-GB.ts
  • integration/templates/next-app-router/src/app/personal-account/page.tsx
  • packages/types/src/clerk.ts
  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/testing/src/playwright/unstable/page-objects/organizationSwitcher.ts
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
packages/localizations/**/*

📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)

Localization files must be placed in 'packages/localizations/'.

Files:

  • packages/localizations/src/utils/enUS_v4.ts
  • packages/localizations/src/en-US.ts
  • packages/localizations/src/en-GB.ts
**/*.{js,ts,tsx,jsx}

📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)

Support multiple Clerk environment variables (CLERK_, NEXT_PUBLIC_CLERK_, etc.) for configuration.

Files:

  • packages/localizations/src/utils/enUS_v4.ts
  • packages/localizations/src/en-US.ts
  • packages/localizations/src/en-GB.ts
  • integration/templates/next-app-router/src/app/personal-account/page.tsx
  • packages/types/src/clerk.ts
  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/testing/src/playwright/unstable/page-objects/organizationSwitcher.ts
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
**/*

⚙️ CodeRabbit Configuration File

**/*: If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes.

Whenever reviewing a pull request, if there are any changes that could impact security, always tag @clerk/security in the PR.

Security-impacting changes include, but are not limited to:

  • Changes to authentication logic or mechanisms (e.g. login, session handling, token issuance)
  • Any modification to access control, authorization checks, or role-based permissions
  • Introduction or modification of hashing algorithms, signature verification, or cryptographic primitives
  • Handling of sensitive data (e.g. passwords, tokens, secrets, PII)
  • Integration with external identity providers (e.g. SSO, OAuth, OpenID Connect)
  • Modifications to security headers, cookie flags, CORS policies, or CSRF protections
  • Bypass mechanisms (e.g. feature flags, testing overrides) that could weaken protections
  • Changes to rate limiting, abuse prevention, or input validation

If you're unsure whether a change is security-relevant, err on the side of caution and tag @clerk/security.

Any time that you tag @clerk/security, please do so explicitly in a code comment, rather than within a collapsed section in a coderabbit comment, such as the "recent review details" section. If you do use the team name in any thinking or non-direct-code-comment content, it can be referred to as "clerk security team" to avoid accidentally printing the tag which sends a notification to the team.

Files:

  • packages/localizations/src/utils/enUS_v4.ts
  • packages/localizations/src/en-US.ts
  • packages/localizations/src/en-GB.ts
  • integration/templates/next-app-router/src/app/personal-account/page.tsx
  • packages/types/src/clerk.ts
  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/testing/src/playwright/unstable/page-objects/organizationSwitcher.ts
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
**/localizations/**/*.ts

⚙️ CodeRabbit Configuration File

**/localizations/**/*.ts: Review the changes to localization files with the following guidelines:

  • Ensure that no existing translations are accidentally removed unless they are being replaced or fixed. If a string is removed, verify that it is intentional and justified.
  • Check that all translations are friendly, formal, or semi-formal. Explicit, offensive, or inappropriate language is not allowed. If you find any potentially offensive language or are unsure, tag the @clerk/sdk-infra team in a separate comment. If you do not intend to tag the team, refer to it as "Clerk SDK Infra team" instead.
  • Use the most up-to-date base localization file (https://github.com/clerk/javascript/blob/main/packages/localizations/src/en-US.ts) to validate changes, ensuring consistency and completeness.
  • Confirm that new translations are accurate, contextually appropriate, and match the intent of the original English strings.
  • Check for formatting issues, such as missing placeholders, incorrect variable usage, or syntax errors.
  • Ensure that all keys are unique and that there are no duplicate or conflicting entries.
  • If you notice missing translations for new keys, flag them for completion.

Files:

  • packages/localizations/src/utils/enUS_v4.ts
  • packages/localizations/src/en-US.ts
  • packages/localizations/src/en-GB.ts
**/*.{jsx,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)

**/*.{jsx,tsx}: Use error boundaries in React components
Minimize re-renders in React components

**/*.{jsx,tsx}: Always use functional components with hooks instead of class components
Follow PascalCase naming for components: UserProfile, NavigationMenu
Keep components focused on a single responsibility - split large components
Limit component size to 150-200 lines; extract logic into custom hooks
Use composition over inheritance - prefer smaller, composable components
Export components as named exports for better tree-shaking
One component per file with matching filename and component name
Use useState for simple state management
Use useReducer for complex state logic
Implement proper state initialization
Use proper state updates with callbacks
Implement proper state cleanup
Use Context API for theme/authentication
Implement proper state selectors
Use proper state normalization
Implement proper state persistence
Use React.memo for expensive components
Implement proper useCallback for handlers
Use proper useMemo for expensive computations
Implement proper virtualization for lists
Use proper code splitting with React.lazy
Implement proper cleanup in useEffect
Use proper refs for DOM access
Implement proper event listener cleanup
Use proper abort controllers for fetch
Implement proper subscription cleanup
Use proper HTML elements
Implement proper ARIA attributes
Use proper heading hierarchy
Implement proper form labels
Use proper button types
Implement proper focus management
Use proper keyboard shortcuts
Implement proper tab order
Use proper skip links
Implement proper focus traps
Implement proper error boundaries
Use proper error logging
Implement proper error recovery
Use proper error messages
Implement proper error fallbacks
Use proper form validation
Implement proper error states
Use proper error messages
Implement proper form submission
Use proper form reset
Use proper component naming
Implement proper file naming
Use proper prop naming
Implement proper...

Files:

  • integration/templates/next-app-router/src/app/personal-account/page.tsx
  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
integration/**

📄 CodeRabbit Inference Engine (.cursor/rules/global.mdc)

Framework integration templates and E2E tests should be placed under the integration/ directory

Files:

  • integration/templates/next-app-router/src/app/personal-account/page.tsx
integration/**/*

📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)

End-to-end tests and integration templates must be located in the 'integration/' directory.

Files:

  • integration/templates/next-app-router/src/app/personal-account/page.tsx
**/*.tsx

📄 CodeRabbit Inference Engine (.cursor/rules/react.mdc)

**/*.tsx: Use proper type definitions for props and state
Leverage TypeScript's type inference where possible
Use proper event types for handlers
Implement proper generic types for reusable components
Use proper type guards for conditional rendering

Files:

  • integration/templates/next-app-router/src/app/personal-account/page.tsx
  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
packages/clerk-js/src/ui/**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/clerk-js-ui.mdc)

packages/clerk-js/src/ui/**/*.{ts,tsx}: Element descriptors should always be camelCase
Use element descriptors in UI components to enable consistent theming and styling via appearance.elements
Element descriptors should generate unique, stable CSS classes for theming
Element descriptors should handle state classes (e.g., cl-loading, cl-active, cl-error, cl-open) automatically based on component state
Do not render hard-coded values; all user-facing strings must be localized using provided localization methods
Use the useLocalizations hook and localizationKeys utility for all text and error messages
Use the styled system (sx prop, theme tokens, responsive values) for custom component styling
Use useCardState for card-level state, useFormState for form-level state, and useLoadingStatus for loading states
Always use handleError utility for API errors and use translateError for localized error messages
Use useFormControl for form field state, implement proper validation, and handle loading and error states in forms
Use localization keys for all form labels and placeholders
Use element descriptors for consistent styling and follow the theme token system
Use the Card and FormContainer patterns for consistent UI structure

Files:

  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
packages/**/*.{test,spec}.{js,jsx,ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)

Unit tests should use Jest or Vitest as the test runner.

Files:

  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
packages/{clerk-js,elements,themes}/**/*.{test,spec}.{js,jsx,ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)

Visual regression testing should be performed for UI components.

Files:

  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
**/*.test.{jsx,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/react.mdc)

**/*.test.{jsx,tsx}: Use React Testing Library
Test component behavior, not implementation
Use proper test queries
Implement proper test isolation
Use proper test coverage
Test component interactions
Use proper test data
Implement proper test setup
Use proper test cleanup
Implement proper test assertions
Use proper test structure

Files:

  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
**/__tests__/**/*.{ts,tsx}

📄 CodeRabbit Inference Engine (.cursor/rules/typescript.mdc)

**/__tests__/**/*.{ts,tsx}: Create type-safe test builders/factories
Use branded types for test isolation
Implement proper mock types that match interfaces

Files:

  • packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx
  • packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx
🔇 Additional comments (19)
packages/localizations/src/utils/enUS_v4.ts (1)

532-532: LGTM: Terminology update aligns with key naming

The change from "Personal account" to "Personal workspace" correctly aligns the display text with the personalWorkspace key name, ensuring consistency in the organization switcher interface.

integration/templates/next-app-router/src/app/personal-account/page.tsx (2)

7-7: LGTM: Console log message updated for consistency

The debug message correctly reflects the new "personal workspace" terminology while maintaining the same logical meaning.


12-12: LGTM: User-facing text updated appropriately

The welcome message properly implements the terminology change from "personal account" to "personal workspace" for consistency across the application.

packages/testing/src/playwright/unstable/page-objects/organizationSwitcher.ts (1)

21-23: LGTM: Test utility method updated consistently

The method rename from expectPersonalAccount to expectPersonalWorkspace and the corresponding text expectation correctly implement the terminology change while maintaining the same testing functionality.

packages/clerk-js/src/ui/components/OrganizationList/__tests__/OrganizationList.test.tsx (8)

31-31: LGTM: Test assertion updated for new terminology

The expectation correctly checks for "Personal workspace" text in the rendered component, maintaining test accuracy with the updated terminology.


36-37: LGTM: Test suite organization updated consistently

The describe block title and test description accurately reflect the "Personal workspace" terminology being tested.


75-75: LGTM: Negative assertion updated appropriately

The test correctly verifies that "Personal workspace" text is not present when hidePersonal is true, maintaining proper test coverage.


83-83: LGTM: Test description reflects updated functionality

The test description accurately describes testing the hiding of "personal workspace" functionality.


98-98: LGTM: Assertion maintains test accuracy

The negative assertion correctly verifies that "Personal workspace" is not displayed when hidden, preserving test integrity.


189-189: LGTM: Test description updated for consistency

The test description properly reflects that the personal workspace should not be shown with force organization selection.


201-201: LGTM: Force organization test assertion updated

The assertion correctly verifies that "Personal workspace" is not displayed when organization selection is forced.


342-342: LGTM: User interaction updated for new text

The click interaction correctly targets the updated "Personal workspace" text, ensuring the test continues to simulate proper user behavior.

packages/types/src/clerk.ts (2)

1611-1613: Documentation terminology update looks good.

The JSDoc comment accurately reflects the updated terminology from "personal account" to "personal workspace" while maintaining clear documentation of the hidePersonal property's functionality.


1703-1705: Consistent terminology update in documentation.

The JSDoc comment properly updates the terminology to match the change in OrganizationSwitcherProps, ensuring consistent documentation across related interfaces.

packages/clerk-js/src/ui/components/OrganizationSwitcher/__tests__/OrganizationSwitcher.test.tsx (5)

5-5: Minor import organization improvement.

The import statement reordering improves code organization without affecting functionality.


34-34: Test assertion updated to match new UI terminology.

The test correctly expects 'Personal workspace' text to match the updated UI component terminology.


151-151: Standalone mode test assertion properly updated.

The test assertion correctly reflects the updated terminology while maintaining the test's purpose of verifying standalone rendering functionality.


198-198: Organization listing test assertion correctly updated.

The test properly expects 'Personal workspace' to appear in the organization list, maintaining test accuracy with the updated UI terminology.


453-453: Personal workspace switching test properly updated.

The user interaction test correctly targets the updated 'Personal workspace' text using an appropriate regex pattern, ensuring the switching functionality test remains accurate.

@LauraBeatris LauraBeatris force-pushed the laura/replace-personal-account-with-personal-workspace-2 branch 3 times, most recently from 8447c28 to 9333d5d Compare July 26, 2025 23:00
@LauraBeatris LauraBeatris changed the title chore(clerk-js,localizations): Replace semantics of Personal Account with Personal Workspace chore(clerk-js,localizations): Deprecate Personal Account semantics with Personal Workspace Jul 26, 2025
Copy link

pkg-pr-new bot commented Jul 26, 2025

Open in StackBlitz

@clerk/agent-toolkit

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

@clerk/astro

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

@clerk/backend

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

@clerk/chrome-extension

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

@clerk/clerk-js

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

@clerk/dev-cli

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

@clerk/elements

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

@clerk/clerk-expo

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

@clerk/expo-passkeys

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

@clerk/express

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

@clerk/fastify

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

@clerk/localizations

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

@clerk/nextjs

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

@clerk/nuxt

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

@clerk/clerk-react

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

@clerk/react-router

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

@clerk/remix

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

@clerk/shared

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

@clerk/tanstack-react-start

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

@clerk/testing

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

@clerk/themes

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

@clerk/types

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

@clerk/upgrade

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

@clerk/vue

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

commit: 7cda61e

expectPersonalAccount: () => {
return expect(page.getByText(/personal account/i)).toBeVisible();
return expect(page.getByText(/personal (workspace|account)/i)).toBeVisible();
Copy link
Member Author

@LauraBeatris LauraBeatris Jul 26, 2025

Choose a reason for hiding this comment

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

Targeting both to avoid breaking changes if clerk-js is not released first or if the app has an older version.

@LauraBeatris LauraBeatris force-pushed the laura/replace-personal-account-with-personal-workspace-2 branch from 9333d5d to 683f9ed Compare July 26, 2025 23:12
@LauraBeatris LauraBeatris force-pushed the laura/replace-personal-account-with-personal-workspace-2 branch from 683f9ed to f5606a6 Compare July 26, 2025 23:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants