Casey Kulm

As part of this, you get access to the gradle maven plugin, and one of it's tasks https://docs.gradle.org/current/userguide/maven_plugin.html#N139B5 is `install` so `$ ./gradlew install` should do it

Not sure why yet, but install seems to not pull in all transitive dependencies. The generated pom file is incomplete

Could this be solved by passing a custom annotation to the `-XepOpt:NullAway:ExcludedFieldAnnotations` complication flag to not check certain fields? To extend upon this, I was hoping to find a way...

After discussing the extended use case above with a co-worker, we decided that wrapping the value in `Optional` can handle the extended case.

To help solve the original problem in this thread, and to even match Kotlin, a pre-baked `@LateInitVar` annotation could be added to NullAway as an ExcludedFieldAnnotation.

Escaping callback hell is one of the great benefits of rxjava/reactive programming. Although it sounds like in this case rather than combining 2 UseCases in the presentation layer, you want...

Those are all implementation details, and should therefore all be contained in the data layer.

The data layer should be the only layer aware of transactions with a database, or anything that has to do with getting/persisting data. In the article describing that data layer......

> "You should of course abstract the technical implementation detail for transactions away from the domain layer" That is correct, but what you said just before it contradicts it... >...

It may be obvious to others, but was not for me that I had to also add `implementation("org.jlleitschuh.gradle:ktlint-gradle:9.4.1")` to the `dependencies` of `buildSrc` to get this working which also required...