What Happened
Great Tables reached v1.0.0 in late September, followed three weeks later by v1.1.0. The 1.x release establishes a settled core API; v1.1.0 fixes more than 60 bugs, largely in number formatting, and improves LaTeX output. [1]
The releases add formatters for fractions, indexes, chemical notation, URLs and email addresses; value-, regex- and predicate-based conditional styling; diverging and row-wise color scales; hierarchical stubs; and decimal alignment. Generated HTML now associates cells with headers and tables with titles and subtitles for screen readers. [1]
Why It Matters to Businesses
Tables are often the point where users inspect a model result or make a decision. More precise formatting and styling can make exceptions easier to spot, while improved table markup can make published results more usable with assistive technology. The latter is a useful improvement, not a substitute for testing the complete application.
These changes are relevant wherever Python-generated tables appear, including data apps and reports built with tools such as Streamlit, Shiny, Jupyter and Quarto. The available release details establish changes to Great Tables, not new releases or compatibility guarantees for Posit, Streamlit, Quarto, Jupyter, Shiny, Gradio, Chainlit, Modal or Replicate.
Kimbodo Engineering Perspective
We would treat Great Tables as a presentation layer, not a place to encode business logic. Calculations, thresholds and access rules should be resolved upstream; table styling should communicate those results consistently. That separation makes an AI application’s displayed evidence easier to test and audit.
How We Would Implement It
- Define a validated pandas or Polars data contract before rendering; keep formatting rules separate from source values.
- Apply named formatters and conditional styles to documented fields, then test boundary values, nulls, negative numbers and unusually long labels. The number-formatting fixes in v1.1.0 make regression checks particularly worthwhile. [1]
- Test HTML output in the target app and with assistive technology. Check header associations, color contrast and whether meaning conveyed by color is also available in text.
- Pin a tested 1.x version and run visual and data-level regression tests before upgrading.
Risks, Costs and Security
Richer styling adds review and maintenance work, especially when palettes or formatting rules change. Clickable URLs and email addresses also warrant validation: do not present untrusted destinations as trusted business links. For AI-generated results, verify the underlying data and calculations independently; a polished table does not make an incorrect answer reliable.
Where Kimbodo Comes In
Kimbodo builds and operates this in production for businesses — see our AI Application Development practice, or Estimate My AI Application.
