alteryx / alteryx/woodwork

Handle `return_invalid_indices` parameter in LatLong and Ordinal validate methods

Open
#1,336 0 comments 0 reactions 0 assignees View on GitHub
new feature
Dominant language
Python
Stars
155
Forks
24
PR merge metrics
No merged PRs in 30d

Description

In #1315, we moved the logical type validation logic to `validate` methods for the Ordinal and LatLong classes. This allows them to be called and validated at woodwork initialization. In that PR, however, we didn't implement the logic to `return_invalid_indices`, which gets used by `TableAccessor.validate_logical_types` to let users know which rows of their dataframe are invalid for their logical type.

We should implement this logic on Ordinal and LatLong logical types, so users can get information about which columns are invalid for that logical type.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.