-
Notifications
You must be signed in to change notification settings - Fork 482
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: refactoring mandatory plugin v2 #6056
base: develop
Are you sure you want to change the base?
Conversation
@@ -0,0 +1,57 @@ | |||
package sliceUtil |
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.
we need to add test cases for these functions
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.
these functions seems useful as we do these operations at multiple places. we will start using these . so proper test cases are required
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.
added
return impl.GetAllPluginMinDataByType("") | ||
} | ||
|
||
func (impl *GlobalPluginRepositoryImpl) GetAllPluginMinDataByType(pluginType string) ([]*PluginParentMetadata, error) { |
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.
pluginType
shouldn't be just string , this method should accept the proper type. make same changes in ENT
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.
The method GetAllPluginMinData()
is being called in multiple places internally. And I introduced GetAllPluginMinDataByType(pluginType string)
recently for a list API. In theGetAllPluginMinData()
we want all types of plugins. In order to reduce the impact area and testing scope, This implementation is being placed
Quality Gate passedIssues Measures |
Description
Fixes #
Checklist:
Does this PR introduce a user-facing change?