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: introduce size variants for light navbar #2760

Merged
merged 4 commits into from
May 17, 2024

Conversation

Lelith
Copy link
Collaborator

@Lelith Lelith commented May 16, 2024

This enables controlling the size of the navbar content via a dedicated prop instead the need to handover specific width sizes.

image

Copy link

vercel bot commented May 16, 2024

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

Name Status Preview Updated (UTC)
forma-36 ✅ Ready (Inspect) Visit Preview May 16, 2024 1:41pm

Copy link

changeset-bot bot commented May 16, 2024

⚠️ No Changeset found

Latest commit: 5d31c9b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@Lelith Lelith marked this pull request as ready for review May 16, 2024 13:41
@Lelith Lelith requested review from damann and a team as code owners May 16, 2024 13:41
@Lelith Lelith requested review from cf-remylenoir, stephanLeece and denkristoffer and removed request for a team May 16, 2024 13:41
@@ -48,12 +51,14 @@ function _Navbar(props: ExpandProps<NavbarProps>, ref: React.Ref<HTMLElement>) {
topRightItems,
contentMaxWidth = '100%',
testId = 'cf-ui-navbar',
className,
variant = 'wide',
Copy link
Collaborator

Choose a reason for hiding this comment

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

Although wide should be our default, we will have a much easier time migrating to the new Layout if we go with fullscreen for now. I'm a bit torn, but since it's an alpha I'm thinking we can always switch it to wide later on. What do you think?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I would rather do the necessary changes now than executing a code-mod later and would go directly with the wide variant as default.
At least this way the fullscreen is a conscious decision from the beginning and we can challenge if its even needed, when it appears to us.
While if we change it later via a code mod we will not think twice over the usage of the fullscreen variant.

But maybe @damann can weight in if fullscreen should be the exception or the norm?

Copy link
Collaborator

Choose a reason for hiding this comment

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

We need fullscreen everywhere we don't have the page cut. So everywhere but 4 screens.

@Lelith Lelith merged commit 6736b26 into feat/navigation_light_mode May 17, 2024
10 of 11 checks passed
@Lelith Lelith deleted the feat/navbar_size_variants branch May 17, 2024 09:50
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.

None yet

2 participants