Skip to content

Conversation

@michael-s-molina
Copy link
Member

SUMMARY

This PR removes the duplicated plugin registration that generates the following type of warning:

Item with key "deck_arc" already exists. You are assigning a new value.
Item with key "deck_arc" already exists. You are assigning a new value.
Item with key "big_number" already exists. You are assigning a new value.
Item with key "box_plot" already exists. You are assigning a new value.

The duplicate registration was necessary when those pages belonged to different React apps. Now, they belong to the same app which makes the registration unnecessary.

The registration should happen only once when the application initializes.

TESTING INSTRUCTIONS

1 - Open any dashboard
2 - Check that the warnings are not there anymore

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

@michael-s-molina michael-s-molina requested a review from a team December 29, 2023 16:47
@codecov
Copy link

codecov bot commented Dec 29, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.14%. Comparing base (863f8bb) to head (dc37653).
Report is 2232 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #26379      +/-   ##
==========================================
- Coverage   69.18%   69.14%   -0.04%     
==========================================
  Files        1946     1946              
  Lines       75988    75986       -2     
  Branches     8479     8479              
==========================================
- Hits        52570    52541      -29     
- Misses      21228    21266      +38     
+ Partials     2190     2179      -11     
Flag Coverage Δ
javascript 56.46% <ø> (-0.08%) ⬇️

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.

@michael-s-molina michael-s-molina merged commit 29633e7 into apache:master Dec 29, 2023
@michael-s-molina michael-s-molina added v3.0 Label added by the release manager to track PRs to be included in the 3.0 branch v3.1 Label added by the release manager to track PRs to be included in the 3.1 branch labels Jan 3, 2024
michael-s-molina added a commit that referenced this pull request Jan 3, 2024
michael-s-molina added a commit that referenced this pull request Jan 3, 2024
@michael-s-molina michael-s-molina removed the v3.0 Label added by the release manager to track PRs to be included in the 3.0 branch label Jan 4, 2024
josedev-union pushed a commit to Ortege-xyz/studio that referenced this pull request Jan 22, 2024
@mistercrunch mistercrunch added 🍒 3.1.0 Cherry-picked to 3.1.0 🍒 3.1.1 Cherry-picked to 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
vinothkumar66 pushed a commit to vinothkumar66/superset that referenced this pull request Nov 11, 2024
@github-actions github-actions bot added 🍒 3.1.2 Cherry-picked to 3.1.2 🍒 3.1.3 Cherry-picked to 3.1.3 🚢 4.0.0 First shipped in 4.0.0 labels Feb 4, 2025
@alephpt
Copy link

alephpt commented Aug 19, 2025

Still seeing this problem in 5.0.0. Any advice?

@rusackas
Copy link
Member

rusackas commented Aug 20, 2025

OMG THANK YOU. That's been nagging at me forever!

LOL, the new comment made me think this was a new PR. This is annoying, and is still an issue. Feel free to file a GitHub issue, or dig into this PR to see what changed since then and investigate a new fix. It'd be appreciated.

@mistercrunch
Copy link
Member

mistercrunch commented Aug 20, 2025

Came here with the same idea -> OMG THANK YOU. That's been nagging at me forever!

@michael-s-molina
Copy link
Member Author

There are only 2 places in master calling setupPlugins():

src/views/App.tsx
src/embedded/index.tsx

@Vitor-Avila @rusackas You might want to check if this call is required for Embedded.

@Vitor-Avila
Copy link
Contributor

There are only 2 places in master calling setupPlugins():

src/views/App.tsx src/embedded/index.tsx

@Vitor-Avila @rusackas You might want to check if this call is required for Embedded.

@rusackas are you aware if that's necessary? I'm not sure

@mistercrunch
Copy link
Member

Both these calls probably shouldn't be module-scoped ...

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/XS v3.1 Label added by the release manager to track PRs to be included in the 3.1 branch 🍒 3.1.0 Cherry-picked to 3.1.0 🍒 3.1.1 Cherry-picked to 3.1.1 🍒 3.1.2 Cherry-picked to 3.1.2 🍒 3.1.3 Cherry-picked to 3.1.3 🚢 4.0.0 First shipped in 4.0.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants