fix: remove duplicate translation keys in common.json#27769
Merged
romitg2 merged 1 commit intocalcom:mainfrom Feb 9, 2026
Merged
fix: remove duplicate translation keys in common.json#27769romitg2 merged 1 commit intocalcom:mainfrom
romitg2 merged 1 commit intocalcom:mainfrom
Conversation
Remove 4 duplicate keys that existed in the English translations file: - routing_forms: identical duplicate removed - submit_feedback: kept "Submit feedback" (consistent casing) - skip_trial: kept "Skip trial" (used as button label) - availability_schedule: kept "Availability schedule" (sentence case), removed duplicate with inconsistent capitalization Fixes calcom#23478
romitg2
approved these changes
Feb 9, 2026
Member
|
Thanks @AhmadYasser1 ! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
common.json)Problem
The
en/common.jsonfile contains 4 keys that appear twice with different values, which causes the second occurrence to silently override the first when the JSON is parsed. This can lead to unexpected translation differences depending on key ordering.Duplicate keys resolved
routing_formssubmit_feedbackskip_trialavailability_scheduleTest plan
Fixes #23478