-
Notifications
You must be signed in to change notification settings - Fork 177
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
Dead code removal #2862
Dead code removal #2862
Conversation
Skipping CI for Draft Pull Request. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2862 +/- ##
==========================================
+ Coverage 77.49% 78.04% +0.54%
==========================================
Files 1109 1094 -15
Lines 23394 23246 -148
Branches 5890 5874 -16
==========================================
+ Hits 18129 18142 +13
+ Misses 5265 5104 -161
... and 25 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
@christianvogt Up to date with confirmed changes/deletions |
@@ -23,8 +24,7 @@ const useDataConnections = (namespace?: string): FetchState<DataConnection[]> => | |||
).then((secrets) => | |||
secrets | |||
.filter<AWSSecretKind>( // TODO: this will make more sense when we have more data connection types | |||
(secret): secret is AWSSecretKind => | |||
!!secret.metadata.labels?.[KnownLabels.DATA_CONNECTION_AWS], // note, always true is fine for now | |||
(secret): secret is AWSSecretKind => isSecretAWSSecretKind(secret), // note, always true is fine for now |
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.
Can you not simply use the function as is?
(secret): secret is AWSSecretKind => isSecretAWSSecretKind(secret), // note, always true is fine for now | |
isSecretAWSSecretKind |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: christianvogt The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Closes: RHOAIENG-2497
Description
Changed code based on feedback from the google doc linked on this ticket.
How Has This Been Tested?
npm run test
Request review criteria:
Self checklist (all need to be checked):
After the PR is posted & before it merges:
main