add support for Any annotation in schema model #594
Merged
Conversation
This file contains 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
the motivation behind this feature is to support column annotations that can have any type, to support use cases like the one described in #592, where custom checks can be applied to any column except for ones that are explicitly defined in the schema model class attributes
Codecov Report
@@ Coverage Diff @@
## master #594 +/- ##
=======================================
Coverage 98.73% 98.73%
=======================================
Files 29 29
Lines 3327 3328 +1
=======================================
+ Hits 3285 3286 +1
Misses 42 42
Continue to review full report at Codecov.
|
cosmicBboy
added a commit
that referenced
this pull request
Sep 5, 2021
* add support for Any annotation in schema model (#594) * add support for Any annotation in schema model the motivation behind this feature is to support column annotations that can have any type, to support use cases like the one described in #592, where custom checks can be applied to any column except for ones that are explicitly defined in the schema model class attributes * update pylint, fix lint * Docs/scaling - Bring Pandera to Spark and Dask (#588) * scaling.rst * edited conf * finished first pass * removing FugueWorkflow * Update index.rst * Update docs/source/scaling.rst Co-authored-by: Niels Bantilan <niels.bantilan@gmail.com> * add support for timezone-aware datetime strategies * fix le/ge strategies with datetime * fix mypy errors Co-authored-by: Niels Bantilan <niels.bantilan@gmail.com> Co-authored-by: Kevin Kho <kdykho@gmail.com>
2 tasks
cosmicBboy
added a commit
that referenced
this pull request
Sep 9, 2021
* Unique keyword arg (#580) * add copy button to docs (#448) * Add missing inplace arg to SchemaModel's validate (#450) * link documentation to github (#449) Co-authored-by: Niels Bantilan <niels.bantilan@gmail.com> * intermediate commit for review by @cosmicBboy * link documentation to github (#449) Co-authored-by: Niels Bantilan <niels.bantilan@gmail.com> * intermediate commit for review by @cosmicBboy * WIP * fix test errors, re-factor allow_duplicates handling * fix io tests * fix docs, remove _allow_duplicates private var * update unique type signature in strategies * completing tests for setters and lazy evaluation of unique kw * small fix for the linting errors * support dataframe-level uniqueness in strategies * add docs, fix error formatting, add multiindex support Co-authored-by: Jean-Francois Zinque <jzinque@gmail.com> Co-authored-by: tfwillems <tfwillems@users.noreply.github.com> Co-authored-by: fkroll8 <13244820+fkrull8@users.noreply.github.com> Co-authored-by: fkroll8 <kent.troutman@tuta.io> * Add support for timezone-aware datetime strategies (#595) * add support for Any annotation in schema model (#594) * add support for Any annotation in schema model the motivation behind this feature is to support column annotations that can have any type, to support use cases like the one described in #592, where custom checks can be applied to any column except for ones that are explicitly defined in the schema model class attributes * update pylint, fix lint * Docs/scaling - Bring Pandera to Spark and Dask (#588) * scaling.rst * edited conf * finished first pass * removing FugueWorkflow * Update index.rst * Update docs/source/scaling.rst Co-authored-by: Niels Bantilan <niels.bantilan@gmail.com> * add support for timezone-aware datetime strategies * fix le/ge strategies with datetime * fix mypy errors Co-authored-by: Niels Bantilan <niels.bantilan@gmail.com> Co-authored-by: Kevin Kho <kdykho@gmail.com> * support frictionless primary keys with multiple fields Co-authored-by: Jean-Francois Zinque <jzinque@gmail.com> Co-authored-by: tfwillems <tfwillems@users.noreply.github.com> Co-authored-by: fkroll8 <13244820+fkrull8@users.noreply.github.com> Co-authored-by: fkroll8 <kent.troutman@tuta.io> Co-authored-by: Kevin Kho <kdykho@gmail.com>
cosmicBboy
added a commit
that referenced
this pull request
Sep 10, 2021
* Unique keyword arg (#580) * add copy button to docs (#448) * Add missing inplace arg to SchemaModel's validate (#450) * link documentation to github (#449) Co-authored-by: Niels Bantilan <niels.bantilan@gmail.com> * intermediate commit for review by @cosmicBboy * link documentation to github (#449) Co-authored-by: Niels Bantilan <niels.bantilan@gmail.com> * intermediate commit for review by @cosmicBboy * WIP * fix test errors, re-factor allow_duplicates handling * fix io tests * fix docs, remove _allow_duplicates private var * update unique type signature in strategies * completing tests for setters and lazy evaluation of unique kw * small fix for the linting errors * support dataframe-level uniqueness in strategies * add docs, fix error formatting, add multiindex support Co-authored-by: Jean-Francois Zinque <jzinque@gmail.com> Co-authored-by: tfwillems <tfwillems@users.noreply.github.com> Co-authored-by: fkroll8 <13244820+fkrull8@users.noreply.github.com> Co-authored-by: fkroll8 <kent.troutman@tuta.io> * Add support for timezone-aware datetime strategies (#595) * add support for Any annotation in schema model (#594) * add support for Any annotation in schema model the motivation behind this feature is to support column annotations that can have any type, to support use cases like the one described in #592, where custom checks can be applied to any column except for ones that are explicitly defined in the schema model class attributes * update pylint, fix lint * Docs/scaling - Bring Pandera to Spark and Dask (#588) * scaling.rst * edited conf * finished first pass * removing FugueWorkflow * Update index.rst * Update docs/source/scaling.rst Co-authored-by: Niels Bantilan <niels.bantilan@gmail.com> * add support for timezone-aware datetime strategies * fix le/ge strategies with datetime * fix mypy errors Co-authored-by: Niels Bantilan <niels.bantilan@gmail.com> Co-authored-by: Kevin Kho <kdykho@gmail.com> * schemas with multi-index columns correctly report errors (#600) fixes #589 * strategies module supports undefined checks in regex columns (#599) * Add support for empty data type annotation in SchemaModel (#602) * remove artifacts of py3.6 support * add support for empty data type annotation in SchemaModel * fix frictionless version in dev dependencies * fix setuptools version instead of frictionless * fix setuptools pinning * remove frictionless from core pandera deps (#609) * support frictionless primary keys with multiple fields (#608) * fix validation of check raising error without message (#613) * docs/requirements.txt pin setuptools (#611) * bump version 0.7.1 Co-authored-by: Jean-Francois Zinque <jzinque@gmail.com> Co-authored-by: tfwillems <tfwillems@users.noreply.github.com> Co-authored-by: fkroll8 <13244820+fkrull8@users.noreply.github.com> Co-authored-by: fkroll8 <kent.troutman@tuta.io> Co-authored-by: Kevin Kho <kdykho@gmail.com>
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.
the motivation behind this feature is to support column annotations
that can have any type, to support use cases like the one described
in #592, where
custom checks can be applied to any column except for ones that
are explicitly defined in the schema model class attributes