fix: Avoid duplicate navigation items

[enjeck]

To reproduce problem:

• Select table or view
• refresh web page
• notice that there are two navigation entries for the active view/table
  Problem also reported at Tables contributor week 2025 Brainstorming outcomes #2089

This PR fixes it by just removing duplicate entries in the store

[blizzz]

Is there a reason why/place where we try to set duplicate tables in first place?

[jancborchardt]

Ran into this last week as well. Didn’t test, but thanks for fixing it!

[benjaminfrueh]

Hi @enjeck and @blizzz
I just ran into this issue too when implementing a new feature, so I decided to look into it quickly.

The issue is caused in the store.js, in the functions loadContextTable() and loadContextView().
These functions try to select a table or view first, and then return if the view or table was found.

const view = this.views.find(view => view.id === id)
if (view) {
    return true
}

The issue is, on page reload, the variable id is a string, not a integer anymore, so it is not able to find the view and duplicates it here with tables.push() and views.push().

I have not looked into why this happens yet or what change caused it, but this duplication could be prevented by making sure the id for searching a view or table is a integer, with e. g. parseInt().

[enjeck]

Hi @enjeck and @blizzz I just ran into this issue too when implementing a new feature, so I decided to look into it quickly.

The issue is caused in the store.js, in the functions loadContextTable() and loadContextView(). These functions try to select a table or view first, and then return if the view or table was found.

const view = this.views.find(view => view.id === id)
if (view) {
    return true
}

The issue is, on page reload, the variable id is a string, not a integer anymore, so it is not able to find the view and duplicates it here with tables.push() and views.push().

I have not looked into why this happens yet or what change caused it, but this duplication could be prevented by making sure the id for searching a view or table is a integer, with e. g. parseInt().

Simpler fix, thanks!