Hey @bertyhell, thanks for raising the PR. I tested it out locally and I see a bug where the URL is going to an undefined state which might cause an issue. I have attached the screenshot below to show how the URL is behaving.

Hey @bertyhell, thanks for the submission! The links of the tree-view are tied to the schema routes and data loading behaviour for the corresponding schemas, and the change you've proposed routes to an undefined schema temporarily to simulate a "closed" state for the node. I wouldn't recommend doing this since it can cause unexpected issue while navigating between databases or schemas.

Another alternative would be to stop the redirect while setting undefined, like so -

if (value === currentSchema) {
      dispatch(updateCurrentSchema(undefined, currentDataSource, false)).then(
        () => {
          dispatch(_push(`/data/${currentDataSource}`));
        }
      );
      return;
      // Clicking the same schema again should collapse the treeview node
    }

but this would still cause re-fetching of schema related info every time an open-close action is triggered, which can be quite expensive.

Given this scenario, I'd recommend you check out the new tree view we have in the improved data-tab UI. It's faster and has a filter that can search across schemas. For the time being we'd like to keep the current behaviour for the legacy one.