feat: Add display.render_mode option to control DataFrame visualization #2413
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 introduces a new configuration option, bigframes.options.display.render_mode, to explicitly control how DataFrames and Series are visualized in Jupyter environments. This change decouples the visualization logic from the execution strategy defined by repr_mode.
Key Changes:
render_modeoption: Added with three supported values:repr_modebehavior: repr_mode remains focused on execution strategy ("head" vs "deferred"). Decoupling these ensures that "head" execution can be paired with any visualization style.Users will see no change in default behavior (Immediate execution + static HTML). However, they now have a clean mechanism to opt-in to the interactive Anywidget experience or force plaintext output by setting bigframes.options.display.render_mode.
Fixes #<479282023> 🦕