Chore - remove "use_table_report" config parameter#1973
Merged
jeromedockes merged 7 commits intoskrub-data:mainfrom Mar 18, 2026
Merged
Chore - remove "use_table_report" config parameter#1973jeromedockes merged 7 commits intoskrub-data:mainfrom
jeromedockes merged 7 commits intoskrub-data:mainfrom
Conversation
Member
they are of a different nature:
|
jeromedockes
approved these changes
Mar 18, 2026
This file contains hidden or 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
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.
Description
This PR removes the "use_table_report" configuration parameter. This config parameter is patching over the default behavior of pandas and polars dataframes in a non-transparent way.
Given it is a big change, it's better if the user changes this using patch_display and unpatch_display instead.
For the moment I have kept the data ops version of this parameter, but maybe we should remove both.