Any plans for a 1.0 release?

[dcutting-neurode]

Since this project is now relatively stable, and other libraries depend on it, are there any plans to make a 1.0 release?

This would mean committing to SemVer fully and would make resolution of large dependency graphs easier.

Because it's currently 0.x, other libraries can't assume SemVer semantics and have to pin to specific patch versions to be safe, which can cause conflicts between multiple upstream libraries.

Is there any reason not to finally move to 1.0?

Thanks!

[mjstephan]

@dcutting-neurode After looking at various database persistence libraries - I find SQLite.swift to be very appealing. I'm worried, though, that this project is semi abandoned, in favor of the newer and actively developed SQLiteData project (https://github.com/pointfreeco/sqlite-data).

Do you have an opinion of whether I should pursue using SQLite.swift, since it does everything I would want (I'm just looking for local caching, not CloudKit sync) or do you think since there has been no real activity here, that this project is just going to become unmaintained and unusable at some point in the future?

I would also love to see this go to 1.0 as a signal that it is stable and still a recommended approach for Swift SQLite persistence (despite their being newer options available).

[dcutting-neurode]

@mjstephan I don't have an informed opinion I'm afraid.

I inherited a project that uses the library and I haven't needed to make many changes to the code that uses it yet. It seems to be working well for our use case.

The lack of any real activity on GitHub and no v1 would make me unlikely to base any new important projects on it. But I also haven't researched the alternatives.

Sorry that's of no help!

[jberkel]

The API hasn't changed much in a long time, so a 1.0 release makes sense. There were some issues regarding error handling and concurrency which should be addressed before, I think

• Perhaps Expression should be renamed to avoid clashing, (Missing argument label 'value:' in call #1277 etc.)