[Bug]: Loading a project twice can trigger a "split()" error message.

[codemile]

What happened?

Steps to reproduce:

• close all projects
• create a blank project
• load a project from a file
• close that loaded project
• load the same project again from a file

Triggers an error message "Failed to load project: ...."

You can't tell what the error was, because that toast is trying to read the fsPath which is undefined producing a Cannot read properties of undefined but if you fix that error, then the error message is XXX shares the same ID (###) and is already open.

Work around solution to bug

• close all projects
• create a blank project
• close the blank project
• create a blank project
• exit Rivet
• start Rivet
• load that project from a file

This works because it appears Rivet is keeping at least 1 last closed project in localStorage. So you need to cycle a few projects to clear state.

What was the expected functionality?

Rivet should be able to load projects from a file if there is no tab visible saying it's already loaded.

Describe your environment

Windows, Node 20.10.0,

Relevant log output

No response

Relevant screenshots

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[codemile]

Here we can see that localStorage has 2 projects in the open state, but only 1 project is currently shown in the UI after the second was closed. I think the Recoil code that pushes state to localStorage is lagging behind by 1 operation, because if you create a new blank project it removes that project that was closed.