Rename the repos API's custom detail name field #5046
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the change
This PR just changes the names of
RepositoryCustomDetails
toHelmPackageRepositoryCustomDetail
andPackageRepositoryCustomDetail
toKappControllerPackageRepositoryCustomDetail
.Benefits
This consistent naming across plugins ensures that the clients can easily identify which custom detail object is using each time. Otherwhise, we would have to just rely on the import path, which can become quite misleading sometimes.
Possible drawbacks
N/A
Applicable issues
RepositoryCustomDetails
to something more specific #5016Additional information
N/A