Settings directory is created twice if two settings files are used about tauri-settings HOT 5 CLOSED

That's a good idea, thanks! I didn't expect you to get active so quickly, appreciate that! :)

from tauri-settings.

Could you elaborate what you mean by two settings files?

from tauri-settings.

Sure. I have two instances of SettingsManager in different modules with different filenames (let's say settings-1.json and settings-2.json) being used in different modules of my (angular) app. They both get initialized at the same time. When the application is started for the first time (i.e. the settings folder doesn't exist yet) only one of the SettingsManagers is initialized successfullly and the other is unedfined (and the error above is shown).

From how I understood the code of this module, there seems to be a race condition in this try-catch block: ensure-settings-file.ts:29. Both instances of SettingsManager check if the folder exists, and then both try to create it. But only one can succeed of course.

I was going to try and fix this, but I haven't been able to get Typescript/Angular to accept my local copy of the module.

from tauri-settings.

From how I understood the code of this module, there seems to be a race condition in this try-catch block: ensure-settings-file.ts:29. Both instances of SettingsManager check if the folder exists, and then both try to create it. But only one can succeed of course.

Hmm, will have to investigate. As a temporary fix, perhaps you can initialize the second SettingsManager once the first one has been initialized using await or .then().

from tauri-settings.

Closing this.

from tauri-settings.