-
Notifications
You must be signed in to change notification settings - Fork 77
sanitizing bug #22
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
sanitizing bug #22
Conversation
|
+1 |
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.
Doesn't this mean that we'll end up with redundant un-sanitized keys in the object? Because we're adding a new key but not deleting the old, un-sanitized one. Seems like we would want to start with an empty accumulator object rather than the existing conf.inCondition one (unless I'm reading this wrong).
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.
Yeah I think you're right. I think it might be worth extracting this transform into a function that can be tested separately.
@VulpesArtificem
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.
He's right, I misunderstood _.transform().
|
+1 |
…rror throw missing credential error
Get graph and task definition persistence working
…k-dep to master * commit 'd46c676a06e09f75545cc32dbe7734c8473a4018': Ignore certain fields on deep comparison of serialized task objects
merge ESXi workflow and add analyze os repo task
fixes bug where not all items are sanitized
https://hwjiraprd01.corp.emc.com/browse/ODR-216