-
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
chore(web): Remove multi provider feature flag #4402
Conversation
NV-2907 Remove the IS_MULTI_PROVIDER_CONFIGURATION_ENABLED feature flag
What?We would like to remove the Why? (Context)The feature flag Definition of Done
|
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.
🌟
import { ISelectPrimaryIntegrationModalProps, SelectPrimaryIntegrationModal } from './SelectPrimaryIntegrationModal'; | ||
|
||
export const useSelectPrimaryIntegrationModal = () => { | ||
const [opened, { open, close }] = useDisclosure(false); | ||
const [isOpened, { open, close }] = useDisclosure(false); |
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.
Subtle but good change in my opinion. 👍🏻
What change does this PR introduce?
This PR removes the multi-provider feature flag from the Web package.
Why was this change needed?
The multi-provider feature has been successfully implemented in production for an adequate length of time.
Other information (Screenshots)
The API and Worker packages are dealt with in #4403