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 UI tweaks #1315

Merged
merged 5 commits into from
Mar 11, 2025
Merged

Feat UI tweaks #1315

merged 5 commits into from
Mar 11, 2025

Conversation

grutt
Copy link
Contributor

@grutt grutt commented Mar 10, 2025

Description

UI Tweaks for upgrade routes

Copy link

vercel bot commented Mar 10, 2025

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

Name Status Preview Comments Updated (UTC)
hatchet-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Mar 10, 2025 3:59pm

@grutt grutt requested review from abelanger5 and mrkaye97 and removed request for abelanger5 March 10, 2025 14:34
@grutt
Copy link
Contributor Author

grutt commented Mar 10, 2025

I think we should consider a more aggressive revision for some of these things at some point... but just want to get these working changes in

Copy link
Contributor

@mrkaye97 mrkaye97 left a comment

Choose a reason for hiding this comment

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

left some comments a couple things - thanks for cleaning this up!

import { Button } from '@/components/ui/button';

export interface BannerProps {
message: React.ReactNode;
Copy link
Contributor

Choose a reason for hiding this comment

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

qq: can we make this a string?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

i think we may want to include an icon or additional links here (i.e. link to migration docs)

Copy link
Contributor

Choose a reason for hiding this comment

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

cool, sounds good

showBanner?: boolean;
}

export const Banner: React.FC<BannerProps> = ({
Copy link
Contributor

Choose a reason for hiding this comment

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

stylistic nit: I've been defining components like this:

export const Banner = ({foo, bar}: BannerProps) => {}

I don't care which we end up going for, but I think we should try to be consistent. WDYT? I kinda like the way I've been doing it because it's a little more terse, but I'm fine either way

Copy link
Contributor Author

Choose a reason for hiding this comment

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

personally prefer React.FC since it adds some additional type safety if needed later

Copy link
Contributor

Choose a reason for hiding this comment

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

ah nice, vs. just JSX.Element? sounds good to me

@abelanger5 abelanger5 merged commit 56795cc into v1 Mar 11, 2025
30 checks passed
@abelanger5 abelanger5 deleted the feat--ui-tweaks branch March 11, 2025 17:47
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