feat: allow definition of multiple dtypes per column in Schema
to facilitate multiple attempts at dtype matching
#17
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 PR enhances the
Schema
class so that multiple column data types can be declared. This doesn't affect previous tests or potential workflows since a dtype can be provided as a string value (previously) or list of strings (new here). Many new tests added to verify the new functionality.We also fix an argument typo across multiple files (the
full_match_dtypes=
arg) and update/improve the clarity of theschema
documentation.Typographical error fixes:
full_match_dtypes=
inpointblank/_interrogation.py
,pointblank/schema.py
, andpointblank/validate.py
files.Documentation improvements:
pointblank/schema.py
to clarify the format for specifying column names and data types.Regex pattern refinements:
pointblank/validate.py
to use[0-9]
instead of\d
for better readability and consistency (also to avoid a deprecation warning)