Status Report Request

[gotjoshua]

Greetings,
I found and forked your project today, and I am quite impressed with the code organization and core functionality! Thanks for sharing this with the FOSS community at large!

I made a list of the first issues that I intend to address in my fork.

I am writing here to invite feedback and to request an official status update from @zxch3n as the maintainer...
Do you have any intentions of picking up the project any time soon?

[zxch3n]

Cool! I'm happy to see that you want to refactor the persistence layer.

I can't spend too much time on this project lately. But I'd love to review your PRs.

Did you consider using something like pouchDB as the new db? It works on both browser and node.

[zxch3n]

I found an article about potential data loss. And a discussion about browsers may delete your IndexedDB database under certain conditions. But it seems like the problem is mainly on Safari's implementation. Maybe we are good on Chromium.

Working on node.js can make tests easier, and it feels safer. But I'm happy to use a browser-only solution if the data safety is guaranteed.

[gotjoshua]

I'm happy to use a browser-only solution if the data safety is guaranteed.

cool, i am into offline first, but not necessarily browser-only...

at the moment i don't see a need for node.js, but i wouldn't like to break the tests by switching to dexie. apparently there are ways to shim indexdb for node (which might be good enough for the tests)

the dexie article you linked to doesn't mention electron, so i think we need to research more about "persistence" of indexdb in electron specifically.

also, my first thought was to add dexie and keep nedb (why change a working system) but my top priority is gitlab integration.
I even consider a data mode that considers gitlab issues to be the source of truth and uses dexie as offline-first and reactive cache

I will try to include flexible settings in each PR (if/when i get that far) so that each new feature proposal will be opt in via the prefs page.

[zxch3n]

I also prefer offline-first. I'd love it to be local-first. I may integrate CRDT someday, but that's another topic.

I guess things that works in Chromium probably works on electron as well.

Feature gating is cool. But it might be hard when you want to change db.

For gitlab integration, it will be awesome if you could abstract a reusable integration layer. So that we can reuse it on github integration/notion integration.

[gotjoshua]

I'd love it to be local-first.

great article (btw) !

i am digging into the concept these days.

abstract a reusable integration layer

sounds good, but i must admit it will take some time till i manage to give this priority

[zxch3n]

Yes. Take your time 😁

[zxch3n]

I converted this issue to a dicussion

[gotjoshua]

Nice, yeah that's more fitting for sure.

Also just want to say that it's great to see that you are still around and into discussions even if you don't have so much bandwidth for coding on this project these days.

[gotjoshua]

some progress...

onezoomin#2 (comment)

[zxch3n]

Great job!