fix(ui): interface language toggle

[dhairyashiil]

What does this PR do?

• Fixes The interface language in event type settings does not work; after saving. #24367
• Fixes CAL-6551

Visual Demo (For contributors especially)

Screen.Recording.2025-10-09.at.12.24.03.AM.mov

[vercel]

@dhairyashiil is attempting to deploy a commit to the cal Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

Updated EventAdvancedTab.tsx to change initialization of the interfaceLanguageVisible state. It now checks whether formMethods.getValues("interfaceLanguage") !== null instead of coercing the value to boolean. This treats an empty string as a visible state, affecting the initial visibility of the interface language UI. The behavior on toggle remains: unchecking sets the value to null; checking sets it to an empty string. No exported or public declarations were altered.

Pre-merge checks and finishing touches

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title clearly identifies the specific UI component being fixed, namely the interface language toggle, and concisely reflects the main purpose of the changeset.
Linked Issues Check	✅ Passed	The change modifies the initialization logic of the interface language toggle so it correctly reflects saved values and persists its state after saving, thereby directly addressing the issue of the toggle not applying or displaying the saved interface language setting (#24367 and CAL-6551).
Out of Scope Changes Check	✅ Passed	The only modification is within the interface language toggle component to adjust its visibility logic, and there are no unrelated or extraneous changes outside the scope of fixing the toggle behavior.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Description Check	✅ Passed	The pull request description clearly references the two issues being addressed and includes a visual demo link that directly relates to the interface language toggle bug, indicating that the description is on-topic and relevant to the changeset. It specifies what the PR does in terms of issue fixes, aligning with the objective of fixing the interface language toggle behavior. Although it does not detail the code changes, it still provides sufficient context for reviewers to understand the purpose of the PR.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[github-actions]

E2E results are ready!

• Workflow #83017.1 latest results

[IbrahimLoveForJS]

is it still available?