1) through your buildscript: https://github.com/saket/press/blob/1cf457a099b747e5cbb6debf75a959856f18b4a7/shared/build.gradle#L29

I got a bug report that my app doesn't support chinese characters when saving a user entered field. I thought retrofit + okhttp all operate using utf 8 (note, I'm not super comfortable with text encodings), but it doesn't seem like this is the case. This seems easily googleable, but most of the responses I get on stackoverflow have no answers, and the searching okhttp/retrofit github also has a bunch of questions that get closed without an answer from the author. My googling, might be failing me, but I did try. Am I missing something? Is this not something that okhttp/retrofit handle? Maybe it's moshi that I'm after? Appreciate any pointers.

Just started playing with

workflow

today and noticed that

workflow-ui/core-android

has both Rx and Coroutines dependencies, are there plans to remove Rx from this artifact?

when using

workflow

, what’s the idiomatic / recommended way to handle transient events (a.ka. the single live event issue 😂)?

I wrote an article about how can we create custom Retrofit CallAdapter to handle the API calls errors and success states. eg

interface Service {
  @GET("topics/{id}")
  suspend fun topic(): NetworkResponse<Topic, CommentsError>
}

class Repository {
  val tpoic = service.getTopic()

    when (tpoic) {
      is NetworkResponse.Success -> // request succeded
      is NetworkResponse.ApiError -> // request failed
      is NetworkResponse.NetworkError -> // network error
      is NetworkResponse.UnknownError -> // unknown error happened
    }
}

https://medium.com/@melegy/create-retrofit-calladapter-for-coroutines-to-handle-response-as-states-c102440de37a

👋 @Zach Klippenstein (he/him) [MOD] My workflow question of the day: can the lifetime of a

Flow

worker go beyond a single

Action

? I want to subscribe to a

Flow

for the lifetime of a workflow, but it looks like any subsequent

action

would cancel the

Flow

immediately and you have to re-subscribe to the

flow

in the next

render

call. I remember reading that it’s possible to subscribe to external event sources, but this is not how I expect

Flow

worker to work so I’m probably doing something wrong.

it’s more likely the first case should be failing too (that property should be marked as transient)

No. Converters don't see the whole response object

After upgrading to

sqldelight 1.3.0

I have this gradle error:

More than one file was found with OS independent path 'META-INF/runtime.kotlin_module'

Searching through build folder reveals that sqldelight and 2 other libraries provide this file. SO is full of advices to exclude these from packaging options, but people also note that this would break reflection. I'm a bit hesitant to do that. Is this really a best solution? Should I file a bug somewhere?

Sorry if this isn’t the right place to ask, but I’m having some trouble with inserting a record without specifying an ID. My table&insert look like:

CREATE TABLE Recipe (
    id INTEGER PRIMARY KEY AUTOINCREMENT,
    title TEXT NOT NULL,
    duration TEXT NOT NULL,
    difficulty TEXT NOT NULL,
    calories INTEGER AS Int NOT NULL
);

insert:
INSERT INTO Recipe (title, duration, difficulty, calories)
VALUES (?, ?, ?, ?);

now, when I call

recipeQueries.insert

, I get a

NOT NULL constraint failed: Recipe.id

.. I’ve been looking around SQLite docs as well, but still can’t figure it out..

Does SqlDelight support

WITH

clause? Trying to do something like this:

WITH existingUser AS (SELECT * FROM user WHERE isRemoved = 0);

[kotlinpoet] Hello! Any hints on how to create generic class reference with wildcard? e.g. given property

PropertySpec.builder("myProp", ClassName(LIBRARY_PACKAGE, "MyClass")

how to update it so I end up with

myProp: MyClass<*>

Tried using

parameterizedBy

with

WildcardTypeName

but it looks like it assumes concrete types

Is there a way to map errors in Retrofit? Whenever I receive an HttpException I want to parse it and turn it into a more domain specific error exception (

sealed class MyAppError : Throwable { ... }

). I can't find a good place to hook this up. Initially I thought I'd write a

CallAdapter.Factory

which simply wraps every adapter, but it needs to somehow get adapter from all other installed factories (itself included) and this'll create a endless recursion.

Hmm. Got a full stack trace? Jesse isn't in here. You could always file a bug.

API 24 min ?

Since @jw is back care to give status update for Moshi future ? 🙂

Would supporting fts5 require changes to sql psi?

Hello everyone, I have some trouble using FTS with sqldelight on Android. It is a multiplatform setup and haven’t tested on ios yet. I have a content table and a fts table pointing to it. Both the tables are populated correctly and I can see all the data when doing

SELECT *

on either but when I try to use

MATCH

on fts table, it always returns empty dataset. Is there any extra step required to enable fts? Am I missing something for the setup? Below are the queries I use to setup tables Create content table

CREATE TABLE dbBook (
  isbn INTEGER NOT NULL PRIMARY KEY,
  title TEXT NOT NULL,
  subtitle TEXT NOT NULL DEFAULT '',
  coverUrl TEXT DEFAULT NULL,
  summary TEXT NOT NULL DEFAULT '',
  authorIds TEXT AS List<Long> NOT NULL,
  revisions TEXT AS List<Long> NOT NULL DEFAULT '',
  publishedOn INTEGER as Date DEFAULT NULL,
  addedAt INTEGER as DateTime NOT NULL DEFAULT ((julianday('now') - 2440587.5) * 86400.0 * 1000)
);

Create fts table

CREATE VIRTUAL TABLE dbBookFts
USING FTS4(
  tokenize=porter,
  content=dbBook,
  isbn INTEGER NOT NULL,
  title TEXT NOT NULL,
  subtitle TEXT NOT NULL,
  summary TEXT NOT NULL
);

Triggers to update fts table

-- Triggers to keep the FTS index up to date.
CREATE TRIGGER dbBook_bu BEFORE UPDATE ON dbBook BEGIN
  DELETE FROM dbBookFts WHERE isbn=old.isbn;
END;
CREATE TRIGGER dbBook_bd BEFORE DELETE ON dbBook BEGIN
  DELETE FROM dbBookFts WHERE isbn=old.isbn;
END;

CREATE TRIGGER dbBook_au AFTER UPDATE ON dbBook BEGIN
  INSERT INTO dbBookFts(isbn, title, subtitle, summary)
  VALUES(new.isbn, new.title, new.subtitle, new.summary);
END;
CREATE TRIGGER dbBook_ai AFTER INSERT ON dbBook BEGIN
  INSERT INTO dbBookFts(isbn, title, subtitle, summary)
  VALUES(new.isbn, new.title, new.subtitle, new.summary);
END;

Query for searching

SELECT dbBook.*
FROM dbBookFts
JOIN dbBook ON dbBookFts.isbn = dbBook.isbn
WHERE dbBookFts MATCH :query;

Even a simple MATCH query is empty

SEELCT * FROM dbBookFts WHERE dbBookFts MATCH :query;

The dispatcher

Does SQLDelight support

Temp Views

?

Does kotlinpoet-metadata have functionality similar to the

Types

and

Elements

classes? There’s some reusable functionality that would be nice, such as an

isSubtypeOf(t1: KmType, t2: KmType

.

I don't recall why

You're saying flowOn(context).map(::executeAsOne), right?

In the Android samples/examples of Workflow (https://github.com/square/workflow-kotlin), at each

showRendering

click listeners are set (as below).

override fun showRendering(rendering: Rendering) {
      messageView.setOnClickListener { rendering.onClick(Unit) }
}

This means it will be set (unnecessarily) at every

Rendering

state change. I don't imagine click listeners to be dynamic very often. What is the reasoning?

it is probably not the greatest thing ever that you can do both because its needlessly confusing

%L i think

Tried it, but not so lucky. This:

val schema = object : SqlDriver.Schema by Database.Schema {
    override fun migrate(driver: SqlDriver, oldVersion: Int, newVersion: Int) {
        appContext.deleteDatabase("mydatabase.db")
        Database.Schema.create(driver)
    }
}

Throws this:

W/SQLiteLog: (28) file unlinked while open: /path/to/mydatabase.db
android.database.sqlite.SQLiteReadOnlyDatabaseException: attempt to write a readonly database (code 1032)
        at android.database.sqlite.SQLiteConnection.nativeExecuteForChangedRowCount(Native Method)
        at android.database.sqlite.SQLiteConnection.executeForChangedRowCount(SQLiteConnection.java:736)
        at android.database.sqlite.SQLiteSession.executeForChangedRowCount(SQLiteSession.java:754)
        at android.database.sqlite.SQLiteStatement.executeUpdateDelete(SQLiteStatement.java:64)
        at android.database.sqlite.SQLiteDatabase.executeSql(SQLiteDatabase.java:1756)
        at android.database.sqlite.SQLiteDatabase.execSQL(SQLiteDatabase.java:1683)
        at android.database.sqlite.SQLiteDatabase.setVersion(SQLiteDatabase.java:950)
        at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:341)
        at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:238)
        at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.getWritableSupportDatabase(FrameworkSQLiteOpenHelper.java:145)
        at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper.getWritableDatabase(FrameworkSQLiteOpenHelper.java:106)
        at com.squareup.sqldelight.android.AndroidSqliteDriver$database$2.invoke(AndroidSqliteDriver.kt:30)
        at com.squareup.sqldelight.android.AndroidSqliteDriver$database$2.invoke(AndroidSqliteDriver.kt:19)
        at kotlin.SynchronizedLazyImpl.getValue(LazyJVM.kt:74)
        at com.squareup.sqldelight.android.AndroidSqliteDriver.getDatabase(Unknown Source:2)
        at com.squareup.sqldelight.android.AndroidSqliteDriver.newTransaction(AndroidSqliteDriver.kt:82)
        at com.squareup.sqldelight.TransacterImpl.transactionWithWrapper(Transacter.kt:208)
        at com.squareup.sqldelight.TransacterImpl.transaction(Transacter.kt:197)
        at com.squareup.sqldelight.Transacter$DefaultImpls.transaction$default(Transacter.kt:82)

Has anyone tried to use SqlDelight's flow extension on Native lately? I have a multiplatform project (Android/iOS), where flow is working w/o issues on Android, but not on iOS. No related logs or crashes. SqlDelight version 1.4.0 (tried with 1.3.0 as well)

That's a bug
Pls file an issue

can anyone create that issue for me, please

they are synchronous so use

withContext