Skip to content
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

chore: Rename SET_ACTIVE_TABS action, add a new action #26147

Merged
merged 1 commit into from
Nov 30, 2023

Conversation

kgabryje
Copy link
Member

SUMMARY

Previously SET_ACTIVE_TABS were in fact changing only 1 active tab in an array of tabs. I renamed it to SET_ACTIVE_TAB and created a new SET_ACTIVE_TABS action which allows us to programatically set active tabs state in the dashboard.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

No functional changes, added unit test for the new action.

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


it('SET_ACTIVE_TABS', () => {
expect(
dashboardStateReducer({ activeTabs: [] }, setActiveTabs(['tab1'])),

Choose a reason for hiding this comment

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

Should this be setActiveTab instead of setActiveTabs?

Copy link
Member Author

Choose a reason for hiding this comment

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

No, it's a new test for the new action

Copy link

codecov bot commented Nov 30, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (f1a6b2f) 69.09% compared to head (ac969bf) 69.09%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #26147   +/-   ##
=======================================
  Coverage   69.09%   69.09%           
=======================================
  Files        1941     1941           
  Lines       75891    75894    +3     
  Branches     8450     8450           
=======================================
+ Hits        52436    52439    +3     
  Misses      21280    21280           
  Partials     2175     2175           
Flag Coverage Δ
javascript 56.27% <100.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.

@kgabryje kgabryje merged commit d00c17d into apache:master Nov 30, 2023
31 checks passed
@michael-s-molina michael-s-molina added the v3.1 Label added by the release manager to track PRs to be included in the 3.1 branch label Nov 30, 2023
michael-s-molina pushed a commit that referenced this pull request Dec 4, 2023
josedev-union pushed a commit to Ortege-xyz/studio that referenced this pull request Jan 22, 2024
@mistercrunch mistercrunch added 🍒 3.1.0 🍒 3.1.1 🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels labels Mar 8, 2024
sfirke pushed a commit to sfirke/superset that referenced this pull request Mar 22, 2024
vinothkumar66 pushed a commit to vinothkumar66/superset that referenced this pull request Nov 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🏷️ bot A label used by `supersetbot` to keep track of which PR where auto-tagged with release labels size/M v3.1 Label added by the release manager to track PRs to be included in the 3.1 branch 🍒 3.1.0 🍒 3.1.1
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants