chore: Removing DASHBOARD_CROSS_FILTERS flag and all that comes with it.#31794
chore: Removing DASHBOARD_CROSS_FILTERS flag and all that comes with it.#31794
Conversation
There was a problem hiding this comment.
Review by Korbit AI
Korbit automatically attempts to detect when you fix issues in new commits.
| Category | Issue | Fix Detected |
|---|---|---|
| Cross Filters Default Behavior Changed ▹ view |
Files scanned
| File Path | Reviewed |
|---|---|
| superset-frontend/packages/superset-ui-core/src/utils/featureFlags.ts | ✅ |
| superset-frontend/src/dashboard/util/crossFilters.ts | ✅ |
| superset-frontend/src/dashboard/components/nativeFilters/utils.ts | ✅ |
| superset-frontend/src/dashboard/components/nativeFilters/FilterBar/Horizontal.tsx | ✅ |
| superset-frontend/src/dataMask/reducer.ts | ✅ |
| superset-frontend/src/dashboard/components/nativeFilters/FilterBar/Vertical.tsx | ✅ |
| superset-frontend/src/dashboard/components/nativeFilters/FilterBar/FilterBarSettings/index.tsx | ✅ |
| superset-frontend/src/components/Chart/ChartContextMenu/ChartContextMenu.tsx | ✅ |
| superset-frontend/src/dashboard/components/Dashboard.jsx | ✅ |
| superset-frontend/src/dashboard/actions/hydrate.js | ✅ |
| superset-frontend/src/dashboard/components/nativeFilters/FilterBar/FilterControls/FilterControls.tsx | ✅ |
| superset-frontend/src/components/Chart/ChartRenderer.jsx | ✅ |
| superset-frontend/src/dashboard/components/nativeFilters/selectors.ts | ✅ |
| superset-frontend/src/dashboard/components/SliceHeaderControls/index.tsx | ✅ |
| superset-frontend/src/dashboard/components/DashboardBuilder/DashboardBuilder.tsx | ✅ |
| superset-frontend/src/dashboard/actions/dashboardState.js | ✅ |
| superset/config.py | ✅ |
Explore our documentation to understand the languages and file types we support and the files we ignore.
Need a new review? Comment
/korbit-reviewon this PR and I'll review your latest changes.Korbit Guide: Usage and Customization
Interacting with Korbit
- You can manually ask Korbit to review your PR using the
/korbit-reviewcommand in a comment at the root of your PR.- You can ask Korbit to generate a new PR description using the
/korbit-generate-pr-descriptioncommand in any comment on your PR.- Too many Korbit comments? I can resolve all my comment threads if you use the
/korbit-resolvecommand in any comment on your PR.- Chat with Korbit on issues we post by tagging @korbit-ai in your reply.
- Help train Korbit to improve your reviews by giving a 👍 or 👎 on the comments Korbit posts.
Customizing Korbit
- Check out our docs on how you can make Korbit work best for you and your team.
- Customize Korbit for your organization through the Korbit Console.
Current Korbit Configuration
General Settings
Setting Value Review Schedule Automatic excluding drafts Max Issue Count 10 Automatic PR Descriptions ❌ Issue Categories
Category Enabled Naming ✅ Database Operations ✅ Documentation ✅ Logging ✅ Error Handling ✅ Systems and Environment ✅ Objects and Data Structures ✅ Readability and Maintainability ✅ Asynchronous Processing ✅ Design Patterns ✅ Third-Party Libraries ✅ Performance ✅ Security ✅ Functionality ✅ Feedback and Support
Note
Korbit Pro is free for open source projects 🎉
Looking to add Korbit to your team? Get started with a free 2 week trial here
9b50bf9 to
dbf8a3c
Compare
| ); | ||
|
|
||
| const showFilterBar = | ||
| (crossFiltersEnabled || nativeFiltersEnabled) && !editMode; |
There was a problem hiding this comment.
was nativeFiltersEnabled already cleaned up?
There was a problem hiding this comment.
Not sure, actually, but it's part of an OR statement, so with crossFiltersEnabled always being true, it doesn't actually matter, so the whole parenthetical will be true, and then showFilterBar can be replaced by !editMode
| expect(screen.queryByRole('img', { name: 'gear' })).not.toBeInTheDocument(); | ||
| }); | ||
|
|
||
| test('Dropdown trigger renders with FF DASHBOARD_CROSS_FILTERS on', async () => { |
There was a problem hiding this comment.
Did you want to update this test as just "Dropdown trigger renders"?
There was a problem hiding this comment.
The dropdown trigger is clicked in other tests so I wasn't worried about keeping it as a separate one. Those other tests would fail if it didn't render.
7d2eff9 to
ab07447
Compare
| showContextMenu: | ||
| props.source === ChartSource.Dashboard && | ||
| !suppressContextMenu && | ||
| (isFeatureEnabled(FeatureFlag.DrillToDetail) || |
There was a problem hiding this comment.
I think we should keep the check for drill to detail here
|
@rusackas I think the tests should pass now |
c2a5df2 to
524753b
Compare
SUMMARY
Approved 5.0 change. The feature is now ready for prime time!
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION