Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(Flyout): Add as prop for Flyout title #2925

Merged
merged 3 commits into from
Sep 4, 2024
Merged

Conversation

sooinc
Copy link
Contributor

@sooinc sooinc commented Aug 9, 2024

Overview

  • Adds optional as prop for Flyout title heading-level

PR Checklist

  • Related to designs:
  • Related to JIRA ticket: [ABC-123]
  • I have run this code to verify it works
  • This PR includes unit tests for the code change
  • This PR includes testing instructions tests for the code change
  • The alpha package of this PR is passing end-to-end tests in all relevant Codecademy repositories

Testing Instructions

  1. See instructions in the Portal PR (link below).

PR Links and Envs

Repository PR Link PR Env
Portal Portal Link Portal Env

@sooinc sooinc changed the title add as prop for Flyout title feat(Flyout): Add as prop for Flyout title Aug 9, 2024
@codecademydev
Copy link
Collaborator

📬Published Alpha Packages:

@codecademy/[email protected]
@codecademy/[email protected]
@codecademy/[email protected]

@codecademydev
Copy link
Collaborator

🚀 Styleguide deploy preview ready!

https://66d1c9c0320e5e94ad0ea3a9--gamut-preview.netlify.app

Deploy Logs

@sooinc sooinc marked this pull request as ready for review August 30, 2024 15:01
@sooinc sooinc requested a review from a team as a code owner August 30, 2024 15:01
@@ -72,7 +72,7 @@ export const Flyout: React.FC<FlyoutProps> = ({
maxWidth="100%"
justifyContent="space-between"
>
<Text as="h2" fontSize={22}>
<Text as="h1" fontSize={22}>
Copy link
Contributor

Choose a reason for hiding this comment

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

do you think it makes sense for this to be configurable and default to h1?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

hmm i had that initially but i couldn't think of a case when title wont be the first in the heading level

Copy link
Contributor

Choose a reason for hiding this comment

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

yeah that makes sense - we can swap to h1 and just refactor if there are any cases of it needing another title level

@sooinc sooinc added the Ship It :shipit: Automerge this PR when possible label Sep 4, 2024
@codecademydev codecademydev merged commit 6bdc1d6 into main Sep 4, 2024
31 of 32 checks passed
@codecademydev codecademydev removed the Ship It :shipit: Automerge this PR when possible label Sep 4, 2024
@codecademydev codecademydev deleted the sc-update-flyout branch September 4, 2024 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants