You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is adding unique_column_names to my Config class the right way to catch non-unique headers? I have 10 columns that match the same regex and duplicated names don't seem to get caught.
Is it possible to add a Checker for the column header in a field definition? I'd like to extend the logic without a complicated regex. In my case, the header can contain a number suffix in an arbitrary format, surrounded by brackets.
I added a Checker in my Config class that loops through the column names. With v0.14.5 I am able to throw a SchemaError in the Checker, have it caught in run_checks() and obtain a formatted line in failure_cases. However, beyond 0.14.5 this try/except of a SchemaError has been removed, resulting in an ugly line within failure_cases that captures a message and none of the other details of the schema error. Is there a different/better way of doing this going forward?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm testing with >=0.14.5
Is adding unique_column_names to my Config class the right way to catch non-unique headers? I have 10 columns that match the same regex and duplicated names don't seem to get caught.
Is it possible to add a Checker for the column header in a field definition? I'd like to extend the logic without a complicated regex. In my case, the header can contain a number suffix in an arbitrary format, surrounded by brackets.
I added a Checker in my Config class that loops through the column names. With v0.14.5 I am able to throw a SchemaError in the Checker, have it caught in run_checks() and obtain a formatted line in failure_cases. However, beyond 0.14.5 this try/except of a SchemaError has been removed, resulting in an ugly line within failure_cases that captures a message and none of the other details of the schema error. Is there a different/better way of doing this going forward?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions