corelibrary that depends on squidb and squidb-annotations. then your android code depends on
squidb-android, and your iOS code depends on
implementation? I believe that only dependencies declared with
apiwill become part of the public api of a shared module
TableModel. Would it be possible to disable this queuing supporting setters and instead only create setters with void return types? This way, I would not need to write extra setters to hide the complete squidb classes within one module nor to write extra setters with void return value...
ModelMethodsthere, those are not converted to class functions correctly... Can try this again, if you want to know the concrete problem (I think it was that those methods stayed static methods...)
declareAdditionalJavahook to generate an entirely new file based on the properties in the model spec. I'm not sure that I see too much value in this though -- an interface abstracts away implementation details so that multiple different implementations can be provided. in this case, there would be a 1-1 correspondence between the interface and its implementation, since a squidb model is really just a data transfer class. any alternative implementation wouldn't be accepted by the squidb database classes (since it expects AbstractModel etc.)
@JvmStaticas is documented there?
ISQLiteOpenHelperthat wrap the corresponding SQLCipher classes. This is usually a pretty direct wrapping; you can find examples of an implementations here, which are the wrappers for the android SQLite bindings project: https://github.com/yahoo/squidb/tree/master/squidb-addons/squidb-sqlite-bindings/src/com/yahoo/squidb/sqlitebindings. then you just override
createOpenHelperin your database to return your SQLCipher implementation, similar to how its documented here: https://github.com/yahoo/squidb/wiki/Using-a-custom-SQLite-build