Delete Chart under "All" in home page doesn't reload interface

[MallikarjunaReddyN]

Bug description

On the home page, there is an option to delete a Chart.

Screenshots/recordings

Superset version

6.0.0

Python version

3.11

Node version

18 or greater

Browser

Chrome

Additional context

No response

Checklist

• I have searched Superset docs and Slack and didn't find a solution to my problem.
• I have searched the GitHub issue tracker and didn't find a similar bug report.
• I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[dosubot]

I took a look at the code and I think I can see the root cause. The issue is in how refreshData works when called without arguments on tabs other than "Mine".

When a chart is deleted, handleChartDelete in utils.tsx calls refreshData() with no arguments for any tab that isn't "Mine":

if (chartFilter === 'Mine') refreshData(filters);
else refreshData();

The refreshData function in the useListViewResource hook works like this:

refreshData: (provideConfig?: FetchDataConfig) => {
  if (state.lastFetchDataConfig) {
    return fetchData(state.lastFetchDataConfig);
  }
  if (provideConfig) {
    return fetchData(provideConfig);
  }
  return null;  // ← does nothing if no lastFetchDataConfig and no provideConfig
},

It first checks state.lastFetchDataConfig. If the data for the current tab was loaded via fetchData (which sets lastFetchDataConfig), the refresh works. But on initial load, ChartTable initializes useListViewResource with pre-fetched data passed directly as initialData [1]:

useListViewResource<Chart>('chart', t('chart'), addDangerToast, true,
  initialTab === TableTab.Mine ? mine : filteredOtherTabData, // ← initial data, not fetched
  [], false);

When initialData is provided, fetchData is never called on the initial render, so lastFetchDataConfig remains undefined. This means the first time a user deletes a chart without having switched tabs (which would trigger getData via the useEffect), refreshData() returns null and nothing happens — the UI doesn't reload.

A fix would be to ensure refreshData always has a valid config to re-fetch with. For example, the handleChartDelete function could always pass a full FetchDataConfig (similar to how it does for the "Mine" tab), or refreshData could fall back to a default config. Alternatively, the ChartTable component could call getData(activeTab) on mount to ensure lastFetchDataConfig is always populated.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}
   

[AoLiGei1221]

I would like to look at this. Please assign to me. Thank you!

[hainenber]

Sure, go for it!