Skip to content

Better handling of column_rewrites when column anme doesn't exist #422

@paddymul

Description

@paddymul

Checks

  • I have checked that this issue has not already been reported.

  • I have confirmed this bug exists on the latest version of Buckaroo.

What type of jupyter notebook were you using (VSCode notebook, google colab, Jupyter Lab, Jupyter notebook). Select multiple if you can reproduce this in multiple environments. If other, please add to description.

Other (please describe in Issue Description)

Reproducible example

ahh
look at buckaroo_pandera

This bug is more for my notes than for public consumption.

Image

Issue description

Buckaroo_pandera depends on column_config_overrides to add coloring to columns with errors.

it refrernces columns that speculatively exist (and will when errors exist).

column_config_overrides blows up when rewriting the speculative name to the a...zz name when the speculative name doesn't exist.

Normally this is useful behaviour, but the error messages should be better. column_config_overrides should complain with sensible messages when a referenced column doesn't exist.

In this case though, we don't want to color the column because we didn't create the color_name column.
there should be an option to silently ignore errors that can be optionally turned on.

Expected behavior

above:

Installed versions

Details ``` Replace this line with the output of buckaroo.debug_packages(). Leave the backticks in place. ```

Jupyter Log output

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions