-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Nv 2679 reusable conditions component #4095
Nv 2679 reusable conditions component #4095
Conversation
NV-2679 🎛️ Reusable Conditions component
What?Create the reusable Notes:
Why? (Context)When: one of my 500+ tenants uses a unique configuration of the provider I want to: set up a dynamic provider configuration for a node in the integration store So I can: send notifications to the specific tenant and to all other tenants, using different provider configurations on behalf of the same node Definition of Done
One condition - Integration store (Figma) Multiple conditions - Integration store (Figma) Add a group - Integration store (Figma) Add a group - Integration store (Figma) Turn into a group - Integration store (Figma) Empty group - Integration store (Figma) Empty group - Integration store (Figma) |
} | ||
`; | ||
|
||
const TooltipContainer = styled.div` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I will make this tooltip reusable and add it to the design system
Note - @davidsoderberg and I agreed that we should merge this now into our feature branch so we can start to more fully test the whole feature e2e + to not delay the depending tasks. |
What change does this PR introduce?
WIP - Initial reusable conditions component
still needs refactoring and tests (all data-test-ids are still just copied)
Why was this change needed?
Other information (Screenshots)