I really considered allowing user to pick between ws4sqlite and Turso, but it will complicate the code a lot for a bit more flexibility, which is not something we should do in this phase.
On why flexibility is complicated, at the last commit of sqliterg-integration, the code has this kind of dependency:
settingsStore
sqlitergExecutorStore
remoteSnippetStore
higherSnippetsStore
dataStateStore
dataManager
Where 6 and 5 and 4 depends on 3, and 3 depends on 2, and 2 depends on 1. Choosing between ws4sqlite and Turso must happen in 1, which propagates to the "upper layers" as well.
Since we have a chance to do everything "brand new", we should also consider using https://github.com/square/svelte-store to simplify the async store logic.
I really considered allowing user to pick between
ws4sqlite
and Turso, but it will complicate the code a lot for a bit more flexibility, which is not something we should do in this phase.On why flexibility is complicated, at the last commit of
sqliterg-integration
, the code has this kind of dependency:settingsStore
sqlitergExecutorStore
remoteSnippetStore
higherSnippetsStore
dataStateStore
dataManager
Where 6 and 5 and 4 depends on 3, and 3 depends on 2, and 2 depends on 1. Choosing between
ws4sqlite
and Turso must happen in 1, which propagates to the "upper layers" as well.