scrub database dump: implement private fields for classes (1/3)#223
Open
scrub database dump: implement private fields for classes (1/3)#223
Conversation
odo-sfct
changed the title
odo-sfct
changed the title
This was referenced Jun 9, 2024
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
1 participant
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.
Part 1 | Part 2 | Part 3
Implements the first part of creating a scrub database dump script is to allow models to declare which fields are sensitive and scrubbed.
Models that have this should extend the interface by inheriting the mixin class and overriding the
privacy_protected_methodmethod. The types are mapped toFakerfake function implementations.