Better handling of json in dataset class #86
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
akamor
requested review from
Travmatth and
tonic-tom
and removed request for
Travmatth
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.
1\ Dataset class now has property for customPiiEntityIds
2\ Dataset class now stores allow/block lists as Dict[str,List[str]], e.g. {'NUMERIC_PII':['\d{4}']} instead of using the 'regexes' and 'strings' properties. This allows for passing the allow/block list values from a dataset directly to redact methods without needing to modify the data.
3\ a new enum listing deprecated pii types