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(dashboard): new integrations page view #7310

Open
wants to merge 70 commits into
base: next
Choose a base branch
from

Conversation

scopsy
Copy link
Contributor

@scopsy scopsy commented Dec 16, 2024

What changed? Why was the change needed?

  • Introduces a new integrations page list view
  • SegmentedControl component as a standalone control
  • TabsList component refactored to use the SegmentedControl
  • Improved some alignments of other pages like workflows and settings page to be according to the design
  • This PR contains a lot of new logo svg files moved from web to show integration icons

Screenshots

CleanShot 2024-12-16 at 15 51 13@2x

Expand for optional sections

Related enterprise PR

Special notes for your reviewer

Copy link

netlify bot commented Dec 16, 2024

Deploy Preview for dashboard-v2-novu-staging failed. Why did it fail? →

Name Link
🔨 Latest commit ca70188
🔍 Latest deploy log https://app.netlify.com/sites/dashboard-v2-novu-staging/deploys/67629765e6029100083b1ba2

@@ -0,0 +1,117 @@
import { Badge } from '@/components/primitives/badge';
Copy link
Contributor

Choose a reason for hiding this comment

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

Please move all the component files from the src/pages/integrations/components directory to the src/components/integrations. If the utils are reusable between the modules please move them to the utils folder, otherwise, keep them under the src/components/integrations.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oh my 🤦‍♂️ was prototyping initially and forgot to move them. I blame keyboard shortcuts for this hehe

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Going to address this in the second PR to avoid merge conflict from hell


<div className="mt-auto flex items-center gap-2">
{integration.channel === 'in_app' && !integration.connected ? (
<Button size="xs" className="h-[26px]" variant="outline" onClick={handleConfigureClick}>
Copy link
Contributor

Choose a reason for hiding this comment

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

if that's the size we would like to use, let's introduce it to the button component

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It's not a size that will be used outside of this component. @twentyone24 I've added this Configure button on the In App provider in case the user hasn't connected yet the integration. Any suggestions on other UX pattern for it? I had to adjust the button size to be in the same size of the Env pill

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants