DirectFileManipulator Update?

[Laharah]

I've been using livesync-bridge for a while but earlier this week I reset my couchdb and reset all the dbs in obsidian. I noticed that livesync-bridge no longer works, it's using the old replicate/pull urls to communicate with couchdb that are now returning a 404.

Digging through the source it looks like DirectFileManipulator is no longer compatible with the new database configuration? I'm not sure as I'm not super familiar with TS or this code base. I did see the todo comment about updating DirectFileManipulator to use LiveSyncDBFunction which makes me think I'm correct.

Looking at the current LiveSync replicators, it looks like they all use pouchdb, which isn't in livesync-bridge.

Are there any plans for updating this? If you know what you want to do and roughly how to do it I'd be happy to give it a shot and try and make a PR. Though your project looks very clean, and I'm not sure you'd want me messing it up with my awful TS 😁

If this doesn't belong here I can move this issue to the livesync-bridge issues page.

[vrtmrz]

Thank you for asking me!

Unfortunately, as you mentioned it lost the compatibilities for the extended configurations.

Now I am making three npm (or jsr) libraries.

Reinvented-wheels, Obsidian-facets, and, livesync-common.
All of them have the tests by vitest.

Indeed, it takes a bit of time. However, I believe that everything would get more rigidity and robustness after this work.

Back into the topic, all your contributions are always welcome! My TS codes were also so awful in the earlier phases. I will not think so about for your codes!

Of course, your contributions will be included into the these libraries.

If this doesn't belong here I can move this issue to the livesync-bridge issues page.

This has been caused the same reason that each libraries has not explicit responsibility. Do not mind to use either here or bridges repo.

Sorry for the rough reply from the mobile phone!