Skip to content

Comments

fix: improve restriction schedule description#22517

Merged
CarinaWolli merged 2 commits intomainfrom
fix/restriction-schedule-description
Jul 15, 2025
Merged

fix: improve restriction schedule description#22517
CarinaWolli merged 2 commits intomainfrom
fix/restriction-schedule-description

Conversation

@CarinaWolli
Copy link
Member

@CarinaWolli CarinaWolli commented Jul 15, 2025

What does this PR do?

Before:
Screenshot 2025-07-15 at 11 19 55 AM

After:
Screenshot 2025-07-15 at 11 19 48 AM

Summary by CodeRabbit

  • Style

    • Minor cleanup of layout classes for improved code consistency.
  • Documentation

    • Updated and clarified the description text for the restriction schedule feature in English localization.

@CarinaWolli CarinaWolli requested a review from ibex088 July 15, 2025 09:20
@CarinaWolli CarinaWolli added the High priority Created by Linear-GitHub Sync label Jul 15, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 15, 2025

Walkthrough

This update modifies the English localization key and description for the restriction schedule feature, simplifying its explanation. In the event availability tab component, the description key for the restriction schedule toggle was updated and a trailing space was removed from a class name string. The toggle’s rendering condition remains unchanged.

Changes

Files/Groups Change Summary
apps/web/public/static/locales/en/common.json Renamed and revised the restriction schedule description key and its text.
packages/features/eventtypes/components/tabs/availability/EventAvailabilityTab.tsx Updated description key for restriction schedule toggle; removed trailing space from className string.

Poem

🐇
A toggle’s tale, now clear and bright,
Words trimmed down just right in sight.
A space removed, a cleaner line,
Making schedules simply shine.
Hop along with code so neat,
Where bunnies and toggles meet!
🥕✨

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

packages/features/eventtypes/components/tabs/availability/EventAvailabilityTab.tsx

Oops! Something went wrong! :(

ESLint: 8.57.1

ESLint couldn't find the plugin "eslint-plugin-playwright".

(The package "eslint-plugin-playwright" was not found when loaded as a Node module from the directory "".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

npm install eslint-plugin-playwright@latest --save-dev

The plugin "eslint-plugin-playwright" was referenced from the config file in ".eslintrc.js".

If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.


📜 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 0337ec4 and 3575282.

📒 Files selected for processing (1)
  • packages/features/eventtypes/components/tabs/availability/EventAvailabilityTab.tsx (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/features/eventtypes/components/tabs/availability/EventAvailabilityTab.tsx
⏰ 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). (2)
  • GitHub Check: Install dependencies / Yarn install & cache
  • GitHub Check: Security Check
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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 docstrings to generate docstrings for this 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.

@CarinaWolli CarinaWolli removed the request for review from ibex088 July 15, 2025 09:20
@graphite-app graphite-app bot requested a review from a team July 15, 2025 09:20
@keithwillcode keithwillcode added consumer core area: core, team members only labels Jul 15, 2025
@dosubot dosubot bot added event-types area: event types, event-types i18n area: i18n, translations labels Jul 15, 2025
@delve-auditor
Copy link

delve-auditor bot commented Jul 15, 2025

No security or compliance issues detected. Reviewed everything up to 3575282.

Security Overview
  • 🔎 Scanned files: 2 changed file(s)
Detected Code Changes
Change Type Relevant files
Enhancement ► EventAvailabilityTab.tsx
    Restore schedule restriction functionality
► common.json
    Update restriction schedule description text
► package.json
    Update version number

Reply to this PR with @delve-auditor followed by a description of what change you want and we'll auto-submit a change to this PR to implement it.

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

🔭 Outside diff range comments (1)
apps/web/public/static/locales/en/common.json (1)

3265-3266: Localizations missing key migration

The old key choose_restriction_schedule_description is still defined in every non-English locale file, so the UI will fall back to a raw string for those languages. You need to remove the deprecated key and add the two new keys with appropriate translations in each pack before merging.

• Affected files:
apps/web/public/static/locales/*/common.json (all language folders)
• Actions required:
– Delete the "choose_restriction_schedule_description" entry in each file
– Add the new keys with corresponding translations:
"choose_restriction_schedule": "<translation>"
"restriction_schedule_description": "<translation>"

Ensure consistency across all locale files before merging.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9674428 and 0337ec4.

📒 Files selected for processing (2)
  • apps/web/public/static/locales/en/common.json (1 hunks)
  • packages/features/eventtypes/components/tabs/availability/EventAvailabilityTab.tsx (2 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: bandhan-majumder
PR: calcom/cal.com#22359
File: packages/lib/server/locales/en/common.json:1336-1339
Timestamp: 2025-07-14T16:31:45.201Z
Learning: When making localization changes for new features, it's often safer to add new strings rather than modify existing ones to avoid breaking existing functionality that depends on the original strings. This approach allows for feature-specific customization while maintaining backward compatibility.
apps/web/public/static/locales/en/common.json (1)

undefined

<retrieved_learning>
Learnt from: bandhan-majumder
PR: #22359
File: packages/lib/server/locales/en/common.json:1336-1339
Timestamp: 2025-07-14T16:31:45.201Z
Learning: When making localization changes for new features, it's often safer to add new strings rather than modify existing ones to avoid breaking existing functionality that depends on the original strings. This approach allows for feature-specific customization while maintaining backward compatibility.
</retrieved_learning>

🧬 Code Graph Analysis (1)
packages/features/eventtypes/components/tabs/availability/EventAvailabilityTab.tsx (2)
apps/api/v2/src/modules/auth/guards/organization-roles/organization-roles.guard.ts (1)
  • isPlatform (40-45)
packages/ui/components/form/index.ts (1)
  • SettingsToggle (36-36)
⏰ 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). (2)
  • GitHub Check: Install dependencies / Yarn install & cache
  • GitHub Check: Security Check
🔇 Additional comments (2)
packages/features/eventtypes/components/tabs/availability/EventAvailabilityTab.tsx (2)

669-669: Minor cleanup: Trailing space removed.

Good cleanup removing the trailing space from the className string.


854-854: Localization key updated to match simplified description.

The description key has been changed from "choose_restriction_schedule_description" to "restriction_schedule_description", which aligns with the PR objective to provide a clearer and more concise description.

Based on the retrieved learnings, when making localization changes, it's often safer to add new strings rather than modify existing ones to avoid breaking functionality. However, since this appears to be a deliberate simplification as mentioned in the PR objectives, this change looks appropriate.

@graphite-app
Copy link

graphite-app bot commented Jul 15, 2025

Graphite Automations

"Add consumer team as reviewer" took an action on this PR • (07/15/25)

1 reviewer was added to this PR based on Keith Williams's automation.

"Add ready-for-e2e label" took an action on this PR • (07/15/25)

1 label was added to this PR based on Keith Williams's automation.

@vercel
Copy link

vercel bot commented Jul 15, 2025

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

2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
cal ⬜️ Ignored (Inspect) Visit Preview Jul 15, 2025 10:47am
cal-eu ⬜️ Ignored (Inspect) Visit Preview Jul 15, 2025 10:47am

Copy link
Member

@alishaz-polymath alishaz-polymath left a comment

Choose a reason for hiding this comment

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

🚀 🚀 🚀

@github-actions
Copy link
Contributor

E2E results are ready!

@CarinaWolli CarinaWolli merged commit afe5fea into main Jul 15, 2025
63 of 65 checks passed
@CarinaWolli CarinaWolli deleted the fix/restriction-schedule-description branch July 15, 2025 12:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

consumer core area: core, team members only event-types area: event types, event-types High priority Created by Linear-GitHub Sync i18n area: i18n, translations ready-for-e2e

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants