forked from IABTechLab/fideslang
-
Notifications
You must be signed in to change notification settings - Fork 2
feat: add data_purposes to Dataset, DatasetCollection, DatasetField #39
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
Merged
+29
−19
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
71172a3
feat: add data_purposes field to Dataset, DatasetCollection, and Data…
22bc6b7
style: reformat with black (CI formatter)
71b5a4e
fix: resolve mypy errors from pydantic dependency drift
9ad251d
fix: properly fix mypy errors instead of suppressing with type: ignore
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
is this deliberately an
Optional[List]that defaults toNonerather than aList[]that defaults to[]?i realize this follows the
data_categoriesconvention above, but i just want to make sure we're not perpetuating a bad design choice. do we imagine thatNonewill signify something different than an empty list ([]) in this case? perhaps the flexibility is good for a model as foundational as this one, because there may be many different applications, and it can be hard to anticipate whether some application may want to distinguishNonefrom[]in the future, even if we don't have that use case now.i can conceive of different meanings for
Nonevs[](e.g.None= 'hasn't yet been reviewed/annotated fordata_purposes';[]= 'reviewed and determined nodata_purposesapply') so i think this choice is justifiable. but just wanted to raise this for thought/discussion/confirmation!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.
OK and now i see the PR note about backward compatibility. that seems like enough justification 👍