Skip to content

[MAINTENANCE] Remove deprecated v0.13.28 V2 API style custom rendering#11833

Open
joshua-stauffer wants to merge 4 commits into
developfrom
remove-deprecated-0-13-28
Open

[MAINTENANCE] Remove deprecated v0.13.28 V2 API style custom rendering#11833
joshua-stauffer wants to merge 4 commits into
developfrom
remove-deprecated-0-13-28

Conversation

@joshua-stauffer
Copy link
Copy Markdown
Member

Summary

Removes the V2 API style custom rendering fallback that was deprecated in v0.13.28 with a removal target of v0.16. We are now well past that removal window (current GX version is 1.16.1).

Removed:

  • ValidationResultsTableContentBlockRenderer._get_legacy_v2_api_style_expectation_string_fn — the classmethod holding the DeprecationWarning, whose entire purpose was to support V2 API style expectation rendering.
  • ValidationResultsTableContentBlockRenderer._get_legacy_v2_api_observed_value — companion helper only meaningful for the deprecated path.
  • The two internal call sites inside _get_content_block_fn that branched to those helpers.
  • The now-unused warnings import.
  • test_ValidationResultsTableContentBlockRenderer_get_content_block_fn_with_v2_api_style_custom_rendering, the one test that solely exercised the deprecated path.

Original deprecation message for context:

V2 API style custom rendering is deprecated as of v0.13.28 and is not fully supported anymore; as it will be removed in v0.16, please transition to V3 API and associated rendering style

Test plan

  • CI passes (lint, types, tests)
  • No external callers — verified via grep across great_expectations, cloud, and gx-runner; the removed symbols were only used internally within the file.

The V2 API style custom rendering path was deprecated in v0.13.28 with a
removal target of v0.16. We are now well past that window (current v1.16.1),
so the fallback method and its companion helper are removed along with the
test that exercised the deprecated path.
Copilot AI review requested due to automatic review settings April 21, 2026 09:54
@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 21, 2026

Deploy Preview for niobium-lead-7998 canceled.

Name Link
🔨 Latest commit fbbd499
🔍 Latest deploy log https://app.netlify.com/projects/niobium-lead-7998/deploys/69e76399f59cf4000838c9c2

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Removes the long-deprecated (v0.13.28) V2 API-style custom rendering fallback from the Data Docs validation results table renderer, aligning the renderer implementation with the current V3 rendering/registry mechanism used across the codebase.

Changes:

  • Removed legacy V2 API-style expectation rendering fallback logic (and associated DeprecationWarning) from ValidationResultsTableContentBlockRenderer.
  • Simplified observed value rendering to rely solely on registered OBSERVED_VALUE renderers (fallback to "--" when absent).
  • Deleted the unit test that exclusively exercised the deprecated V2 custom rendering path.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
great_expectations/render/renderer/content_block/validation_results_table_content_block.py Removes V2 legacy helper methods/import and legacy branching in _get_content_block_fn / observed value rendering.
tests/render/test_render_ValidationResultsTableContentBlockRenderer.py Removes the test that validated the deprecated V2 API-style custom rendering behavior.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 21, 2026

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 84.67%. Comparing base (6f966e1) to head (fbbd499).
⚠️ Report is 28 commits behind head on develop.
✅ All tests successful. No failed tests found.

Files with missing lines Patch % Lines
great_expectations/compatibility/pyarrow.py 0.00% 1 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop   #11833      +/-   ##
===========================================
- Coverage    84.69%   84.67%   -0.02%     
===========================================
  Files          471      471              
  Lines        39189    39170      -19     
===========================================
- Hits         33190    33169      -21     
- Misses        5999     6001       +2     
Flag Coverage Δ
3.10 73.60% <0.00%> (+0.02%) ⬆️
3.10 athena ?
3.10 aws_deps ?
3.10 big ?
3.10 clickhouse ?
3.10 filesystem ?
3.10 openpyxl or pyarrow or project or sqlite or aws_creds ?
3.10 postgresql ?
3.10 singlestore ?
3.10 spark_connect ?
3.10 sql_server ?
3.10 trino ?
3.11 73.63% <0.00%> (+0.02%) ⬆️
3.11 athena ?
3.11 aws_deps ?
3.11 big ?
3.11 clickhouse ?
3.11 filesystem ?
3.11 mysql ?
3.11 openpyxl or pyarrow or project or sqlite or aws_creds ?
3.11 postgresql ?
3.11 singlestore ?
3.11 spark_connect ?
3.11 sql_server ?
3.11 trino ?
3.12 73.65% <0.00%> (+0.02%) ⬆️
3.12 athena ?
3.12 aws_deps ?
3.12 big ?
3.12 filesystem ?
3.12 mysql ?
3.12 openpyxl or pyarrow or project or sqlite or aws_creds ?
3.12 postgresql ?
3.12 singlestore ?
3.12 spark_connect ?
3.12 sql_server ?
3.12 trino ?
3.13 73.65% <0.00%> (+0.02%) ⬆️
3.13 athena 41.92% <0.00%> (+<0.01%) ⬆️
3.13 aws_deps 45.18% <0.00%> (+<0.01%) ⬆️
3.13 big 55.22% <0.00%> (-0.03%) ⬇️
3.13 bigquery 51.25% <0.00%> (+0.01%) ⬆️
3.13 clickhouse 41.93% <0.00%> (+<0.01%) ⬆️
3.13 databricks 53.05% <0.00%> (+0.01%) ⬆️
3.13 filesystem 64.36% <0.00%> (+0.01%) ⬆️
3.13 gx-redshift 51.40% <0.00%> (+0.01%) ⬆️
3.13 mysql 51.80% <0.00%> (+0.01%) ⬆️
3.13 openpyxl or pyarrow or project or sqlite or aws_creds 59.96% <0.00%> (+0.01%) ⬆️
3.13 postgresql 55.22% <0.00%> (+0.01%) ⬆️
3.13 singlestore 46.93% <0.00%> (+<0.01%) ⬆️
3.13 snowflake 53.89% <0.00%> (+0.01%) ⬆️
3.13 spark 55.91% <0.00%> (+0.01%) ⬆️
3.13 spark_connect 46.84% <0.00%> (+<0.01%) ⬆️
3.13 sql_server 53.23% <0.00%> (+0.01%) ⬆️
3.13 trino 48.74% <0.00%> (+0.01%) ⬆️
cloud 0.00% <0.00%> (ø)
docs-basic 59.51% <0.00%> (+0.01%) ⬆️
docs-creds-needed 58.12% <0.00%> (+0.01%) ⬆️
docs-spark 57.56% <0.00%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

The continue-on-error flag originally added in #11829 was dropped when
#11822 refactored the pact-contract-check into its own job. Without it,
PRs fail whenever Mercury has not verified the new consumer pact within
the 10-minute retry window — which is a timing/infrastructure signal,
not an indicator that the PR itself has regressed a contract.
Copilot AI review requested due to automatic review settings April 21, 2026 11:21
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated no new comments.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

pyarrow 24.0.0 started shipping stubs that declare the top-level
`pyarrow` as a specific Module subtype, making the `pyarrow =
PYARROW_NOT_IMPORTED` fallback fail mypy's [assignment] check. The
fallback only runs when the import fails, so silencing the assignment
error with a targeted type-ignore matches the existing pattern elsewhere
in this compatibility/ package.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants