fix(FN-XXXX): stop engine creating nested .fusion/.fusion dir
PluginStore expects a project-root path and appends `.fusion` itself, but the in-process runtime was handing it the already-resolved `.fusion` directory — producing a spurious `.fusion/.fusion/fusion.db` on every engine startup. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
5
.changeset/fix-nested-fusion-dir.md
Normal file
5
.changeset/fix-nested-fusion-dir.md
Normal file
@@ -0,0 +1,5 @@
|
|||||||
|
---
|
||||||
|
"@runfusion/fusion": patch
|
||||||
|
---
|
||||||
|
|
||||||
|
Fix engine startup creating a spurious `.fusion/.fusion/fusion.db` under each project root. The in-process runtime was passing the project's `.fusion` directory to PluginStore, which internally appends `.fusion` again, producing a nested empty database alongside the real one. PluginStore now receives the project root, matching every other call site.
|
||||||
@@ -170,7 +170,7 @@ export class InProcessRuntime
|
|||||||
this.messageStore = new MessageStoreClass(this.taskStore.getDatabase());
|
this.messageStore = new MessageStoreClass(this.taskStore.getDatabase());
|
||||||
|
|
||||||
// 2. Initialize Plugin system (PluginStore + PluginLoader + PluginRunner)
|
// 2. Initialize Plugin system (PluginStore + PluginLoader + PluginRunner)
|
||||||
this.pluginStore = new PluginStoreClass(this.taskStore.getFusionDir());
|
this.pluginStore = new PluginStoreClass(this.config.workingDirectory);
|
||||||
await this.pluginStore.init();
|
await this.pluginStore.init();
|
||||||
|
|
||||||
this.pluginLoader = new PluginLoaderClass({
|
this.pluginLoader = new PluginLoaderClass({
|
||||||
|
|||||||
Reference in New Issue
Block a user