Skip to content
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

fix(localizations): Fix de-DE key socialButtonsBlockButtonManyInView #4878

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

christiankaindl
Copy link

@christiankaindl christiankaindl commented Jan 13, 2025

Description

A previous change changed the label for buttons when multiple SSO providers are active from the provider name to a long string, which breaks the layout. This change brings the label for the key socialButtonsBlockButtonManyInView back to the desired one and in line with other languages.

The previous value roughly translates to "Too many buttons are shown. Reduce amount of buttons to continue"—this doesn't make any sense and is unique to the German translations. The broken string was introduced in this commit, together with other changes, so it seems it fell through the cracks: b9a5bea#diff-96883e89b065cc0abf16578b55e5a53c76a77b62d3ea953fa4e6064c29da93aaR550

Without the fix, the SignIn component with German translations looks like this:
Screenshot 2025-01-13 at 09 31 43

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:

A previous change changed the label for buttons when multiple SSO providers are active from the provider name to a long string, which breaks the layout. This change brings the label for the key `socialButtonsBlockButtonManyInView` back to the desired one.

The broken string was introduced here: clerk@b9a5bea#diff-96883e89b065cc0abf16578b55e5a53c76a77b62d3ea953fa4e6064c29da93aaR550
Copy link

changeset-bot bot commented Jan 13, 2025

⚠️ No Changeset found

Latest commit: 12a2e57

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

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

Click here to learn what changesets are, and how to add one.

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

Copy link

vercel bot commented Jan 13, 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 Jan 13, 2025 8:39am

@panteliselef
Copy link
Member

Hey @christiankaindl thanks for your contribution. This seems to be affecting more package so I opened #4887 to address that. Also the new PR will force the property to match a new pattern I order to avoid any similar issues in the future.

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.

3 participants