Looking at this again, there's a few issues with this code being tied to the UI. Because this is in the init function, it's only called once. Opening new projects in new windows or changing projects wont cause this to be updated. Also this code is specific to the WelcomeWindow, which I dont think this incoming change fits in with. If indexing fails, there's no way to try it again.

Due to these reasons, I think this feature might be a good candidate for creating a service. VSCode has this in a WorkspacesService, which is responsible for workspace management, recently opened workspaces, event handling and persistence. With a service, we can hook into relevant events to update as needed and we can invoke retries when necessary. This will also help with our separation of concerns between UI and functionality. Thoughts?

I tested and the indexing happens whenever you open the app, even if the welcome window is not opened

All the window views here are initialized at the start of the application. One of the problems is that it only happens once, even if we open new projects, windows, etc. If the indexing fails, then it wont ever be retried. This code in general shouldnt be tied to the welcome window either. For this PR, I'd say it's fine until we get our services defined more, but I'd like to come back to this and move the code into a service to address these issues.

Got it, thanks. I'll make those changes.

@FastestMolasses I implemented the requested changes, please let me know if there's anything else you want me to change