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: add infrastructure tabs and content #2588

Merged
merged 1 commit into from
Sep 3, 2024
Merged

Conversation

wesbillman
Copy link
Collaborator

Fixes #2552

Screenshot 2024-09-03 at 1 44 20 PM
Screenshot 2024-09-03 at 1 44 27 PM
Screenshot 2024-09-03 at 1 44 30 PM
Screenshot 2024-09-03 at 1 44 35 PM

@wesbillman wesbillman requested review from a team and jonathanj-square and removed request for a team September 3, 2024 20:53
This was referenced Sep 3, 2024
@wesbillman wesbillman force-pushed the add-infrastructure-tabs branch from ee9bf31 to 6e70668 Compare September 3, 2024 20:56
Comment on lines +10 to +12
playwright-report/
test-results/

Copy link
Contributor

Choose a reason for hiding this comment

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

thanks for catching this!

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

You bet! I think there are going to be other similar issues after the relocating of all these files.

className?: string
}

export const List = <T,>({ items, renderItem, onClick, className }: ListProps<T>) => {
Copy link
Contributor

Choose a reason for hiding this comment

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

Did you mean to remove this , or is that doing some fancy JS magic I haven't learned yet? :)

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 think the , is required for the component to parse correctly. Removing it causes all kinds of errors 😂 . I think it's just a react generic component feature.

Copy link
Contributor

Choose a reason for hiding this comment

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

oh wow that's good to know!

<li
key={index}
className={`relative flex justify-between gap-x-6 p-4 ${onClick ? 'cursor-pointer hover:bg-gray-50 dark:hover:bg-gray-700' : ''}`}
onClick={onClick ? () => onClick(item) : undefined}
Copy link
Contributor

Choose a reason for hiding this comment

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

Just to confirm, if you use this component without an onClick, does passing undefined into this prop definitely not throw a runtime error? I wasn't sure if it was safe to pass undefined to a fn prop.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

yeah should be ok. All the current stuff is using it without an onClick.

<div className='flex gap-x-4 items-center w-1/2'>
<div className='whitespace-nowrap'>
<div className='flex gap-x-2 items-center'>{route.module}</div>
<p className='mt-1 flex text-xs leading-5 text-gray-400 font-roboto-mono'>{route.endpoint}</p>
Copy link
Contributor

@deniseli deniseli Sep 3, 2024

Choose a reason for hiding this comment

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

nit: this shade of gray feels good for dark mode but a little eye-strainy for light mode. What do you think about bumping it up to 600 when mode=light?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Bumped to 500 which feels pretty good too

Comment on lines 11 to 13
idle: 'text-gray-500 bg-gray-100/10',
success: 'text-green-400 bg-green-400/10',
error: 'text-rose-400 bg-rose-400/10',
Copy link
Contributor

Choose a reason for hiding this comment

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

I feel like these also look great on dark mode but feel a little light for light mode. 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.

Good call! Updated.

@wesbillman wesbillman force-pushed the add-infrastructure-tabs branch from 6e70668 to 78c6c0f Compare September 3, 2024 21:29
@wesbillman wesbillman added this pull request to the merge queue Sep 3, 2024
Merged via the queue into main with commit 1aa1350 Sep 3, 2024
23 checks passed
@wesbillman wesbillman deleted the add-infrastructure-tabs branch September 3, 2024 21:39
@alecthomas
Copy link
Collaborator

GLORIOUS!

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.

Display ftl status information in Infrastructure section
3 participants