Skip to content
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

fix(cli): ScrubSensitiveData to scrub recursively #537

Closed
wants to merge 2 commits into from

Conversation

redgoat650
Copy link

No description provided.

@Shrekster Shrekster changed the title Fix ScrubSensitiveData to scrub recursively fix(cli): ScrubSensitiveData to scrub recursively Jan 25, 2024
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (c56d330) 75.86% compared to head (5484afd) 75.84%.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #537      +/-   ##
==========================================
- Coverage   75.86%   75.84%   -0.03%     
==========================================
  Files         465      465              
  Lines       37171    37179       +8     
==========================================
- Hits        28201    28197       -4     
- Misses       7047     7053       +6     
- Partials     1923     1929       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@@ -12,7 +12,11 @@ import (
type S struct {
SomePassword1 string `kopia:"sensitive"`
NonPassword string
Inner *Q
InnerPtr *Q

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does extending the struct cover the desired cases? or should the text be extended with additional "input cases"?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I initially started writing a table driven test with inputs and expected outputs, but concluded it was a lot of boilerplate to accomplish the same conditions: instead of defining different test structs for the different test cases we could get the same coverage by adding the newly-handled field types in the existing test struct.

Copy link

@julio-lopez julio-lopez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1: LG 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants