Added obfuscate feature for replacing source data with **** #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request adds a new property obfuscation feature to the
DotPathQLlibrary, allowing users to mask sensitive data fields (such as passwords or SSNs) with "****" while preserving the structure of the original object. The update includes changes to the core implementation, factory methods, and test coverage, as well as documentation enhancements in theREADME.md.New Feature: Property Obfuscation
obfuscatemethod toDotPathQL, enabling users to specify paths whose values should be replaced with "****".addDefaultObfuscatePaths.PathExcludeclass and factory to support obfuscation mode, ensuring the same filtering logic can be reused for masking values [1] [2] [3] [4].Other Improvements