-
-
Notifications
You must be signed in to change notification settings - Fork 658
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: Delete dependency api #4824
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
@@ -45,7 +45,7 @@ export const AddDependency: FC<IAddDependencyProps> = ({ | |||
onChange={e => setParent(trim(e.target.value))} | |||
/> | |||
<PermissionButton | |||
permission={CREATE_FEATURE} | |||
permission={UPDATE_FEATURE} |
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.
eventually we'll get a permission for managing dependencies, for now UPDATE_FEATURE is more correct than CREATE_FEATURE
openApiService, | ||
}: DependentFeaturesServices, | ||
startTransaction: TransactionCreator<UnleashTransaction>, | ||
) { | ||
super(config); | ||
this.transactionalDependentFeaturesService = | ||
transactionalDependentFeaturesService; | ||
this.dependentFeaturesService = dependentFeaturesService; |
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.
deletion does not have to be transactional as there's only one DB operation involved
About the changes
API for deleting feature dependency
Important files
Discussion points