fix: remove invalid nested anchor inside button in call history empty state#27506
Merged
Udit-takkar merged 2 commits intocalcom:mainfrom Feb 2, 2026
Merged
fix: remove invalid nested anchor inside button in call history empty state#27506Udit-takkar merged 2 commits intocalcom:mainfrom
Udit-takkar merged 2 commits intocalcom:mainfrom
Conversation
Contributor
|
Hey there and thank you for opening this pull request! 👋🏼 We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted. Details: |
Udit-takkar
approved these changes
Feb 2, 2026
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
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.
Problem:
The "Create Cal.ai workflow" button in the call history empty state had a component nested inside
Solution:
Use Button's href prop instead of nesting Link. When href is passed, Button renders as (styled as button) rather than
Video demo: (after fix)
Screen.Recording.2026-02-02.at.5.39.49.PM.mov
Image Demo (if applicable):
Mandatory Tasks (DO NOT REMOVE)
How should this be tested?
Checklist