Skip to content

feat(viz-type): Ag grid table plugin Integration #33517

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 140 commits into
base: master
Choose a base branch
from

Conversation

amaannawab923
Copy link
Contributor

@amaannawab923 amaannawab923 commented May 19, 2025

SUMMARY

FEATURE_CHART_PLUGINS_EXPERIMENTAL=true

This pr integrates the whole ag grid table with parity to Superset Tables with all of its functionalities as listed below:

  1. Server Pagination
  2. Server Side Sorting
  3. Server Side Search
  4. Server Side Page Size Change
  5. Percentage Metrics
  6. Row limits constraints as per Superset table (Max: 500k rows with server pagination & 100k rows without server pagination)
  7. Time Comparison with Time Shift Controls as per Superset table
  8. Timestamp Formatting
  9. Allowing the columns to be re arranged
    10 . Column Customisation - ( Column Alignment , Formatting , Currency Formatting)
  10. Cell bars
  11. Custom Conditional Formatter
  12. Cross Filtering

Below is the current State of Ag Grid table with all of the features:

Screenshot 2025-06-12 at 10 45 45 AM

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

  • Has associated issue:
  • Required feature flags:
  • Changes UI
  • Includes DB Migration (follow approval process in SIP-59)
    • Migration is atomic, supports rollback & is backwards-compatible
    • Confirm DB migration upgrade and downgrade tested
    • Runtime estimates and downtime expectations provided
  • Introduces new feature or API
  • Removes existing feature or API

Copy link

korbit-ai bot commented May 19, 2025

Based on your review schedule, I'll hold off on reviewing this PR until it's marked as ready for review. If you'd like me to take a look now, comment /korbit-review.

Your admin can change your review schedule in the Korbit Console

amaannawab923 and others added 8 commits June 23, 2025 18:54
* Temp

* Fixing drill by

* Enterprise checkpoint

* Update context instead of custom meta as per preset

* Open source cross filter update

* Revert 1

* Remove enterprise

* Revert from ent

* Package lock
* fix(logo): fix logo url typo (apache#33867)

* chore(Icons): Add UsergroupAddOutlined icon (apache#33866)

* fix(api): Added uuid as a valid search column (apache#33833)

* fix(native filters): Make the Apply button available after click on Clear All (apache#33834)

* build(deps): remove legacy browser polyfills (apache#33853)

Signed-off-by: hainenber <[email protected]>

* build(dev-deps): update `fetch-mock` to v11 (apache#33854)

Signed-off-by: hainenber <[email protected]>

* build(be/deps): replace `importlib_metadata` usage with native  Python 3.10+ `importlib.metadata`  (apache#33868)

Signed-off-by: hainenber <[email protected]>

* chore: Updates files related to 5.0.0 release (apache#33869)

* chore(docs): bump references to docker image versions upon release of 5.0.0 (apache#33872)

---------

Signed-off-by: hainenber <[email protected]>
Co-authored-by: Levis Mbote <[email protected]>
Co-authored-by: Enzo Martellucci <[email protected]>
Co-authored-by: Paul Rhodes <[email protected]>
Co-authored-by: Vitor Avila <[email protected]>
Co-authored-by: Đỗ Trọng Hải <[email protected]>
Co-authored-by: Michael S. Molina <[email protected]>
Co-authored-by: Sam Firke <[email protected]>
@github-actions github-actions bot added api Related to the REST API doc Namespace | Anything related to documentation labels Jun 24, 2025
@github-actions github-actions bot removed api Related to the REST API doc Namespace | Anything related to documentation labels Jun 24, 2025
@@ -27,6 +27,8 @@
"@react-icons/all-files": "^4.1.0",
"@types/d3-array": "^2.9.0",
"@types/react-table": "^7.7.20",
"ag-grid-community": "^33.1.1",
Copy link
Member

Choose a reason for hiding this comment

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

should this be in peerDependencies? Also wondering if we need to rethink where the main deps should live and how the peerDeps should be set. I think what makes more sense is to add the main dep in @superset-ui/core and have the main package/app AND plugins set them as peerDep.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants