Skip to content

Commit

Permalink
chore: fixed headers in user setting tabs grafana#4335
Browse files Browse the repository at this point in the history
Signed-off-by: Shyamal Prajapati <[email protected]>
  • Loading branch information
shyamal2411 committed Oct 14, 2024
1 parent 10b532c commit 8e37aeb
Showing 1 changed file with 6 additions and 6 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -72,9 +72,9 @@ export const Tabs = ({
/>
)}
{showGoogleCalendarTab && (
<Tab
<Tab"Google Calendar"
active={activeTab === UserSettingsTab.GoogleCalendar}
label="Google Calendar"
label=
key={UserSettingsTab.GoogleCalendar}
onChangeTab={getTabClickHandler(UserSettingsTab.GoogleCalendar)}
data-testid="google-calendar-tab"
Expand All @@ -90,7 +90,7 @@ export const Tabs = ({
{showMobileAppConnectionTab && (
<Tab
active={activeTab === UserSettingsTab.MobileAppConnection}
label="Mobile App Connection"
label="Mobile App"
key={UserSettingsTab.MobileAppConnection}
onChangeTab={getTabClickHandler(UserSettingsTab.MobileAppConnection)}
data-testid="tab-mobile-app"
Expand All @@ -99,7 +99,7 @@ export const Tabs = ({
{showSlackConnectionTab && (
<Tab
active={activeTab === UserSettingsTab.SlackInfo}
label="Slack Connection"
label="Slack"
key={UserSettingsTab.SlackInfo}
onChangeTab={getTabClickHandler(UserSettingsTab.SlackInfo)}
data-testid="tab-slack"
Expand All @@ -108,7 +108,7 @@ export const Tabs = ({
{showTelegramConnectionTab && (
<Tab
active={activeTab === UserSettingsTab.TelegramInfo}
label="Telegram Connection"
label="Telegram"
key={UserSettingsTab.TelegramInfo}
onChangeTab={getTabClickHandler(UserSettingsTab.TelegramInfo)}
data-testid="tab-telegram"
Expand All @@ -117,7 +117,7 @@ export const Tabs = ({
{showMsTeamsConnectionTab && (
<Tab
active={activeTab === UserSettingsTab.MSTeamsInfo}
label="Ms Teams Connection"
label="MS Teams"
key={UserSettingsTab.MSTeamsInfo}
onChangeTab={getTabClickHandler(UserSettingsTab.MSTeamsInfo)}
data-testid="tab-msteams"
Expand Down

0 comments on commit 8e37aeb

Please sign in to comment.