For those that are interested in a explicit DI library (no magic ✨) that is written in Kotlin K there is Kapsule 💊 (https://blog.gouline.net/kapsule-minimalist-dependency-injection-for-kotlin-ed3e344d60ed). In some ways Kapsule does DI in similar ways that TornadoFX (https://edvin.gitbooks.io/tornadofx-guide/content/20.%20Dependency%20Injection.html) does via delegates. 😀 ✅

TIL https://en.m.wikipedia.org/wiki/QUIC

Hi all. I just created https://github.com/vjames19/kotlin-futures "A better CompletableFuture API for kotlin using Extension Functions". Feedback would be appreciated!

That still seems verbose compared to rxjava or coroutines... Though definitely less so than Java futures ☺️

We use Dagger2 and it works, although IntelliJ IDEA support is less than ideal (need a manual gradle recompile after dependency changes or

clean

runs) - that example would be very helpful

I really like that there is practically no magic in Dagger 2 - it simply generates classes that then compile

the generated code is also very simple (there may be a lot of it - that's why we use DI in the first place - but it's conceptually very simple)

I'm not such a Spring hater as some here.. but Dagger 2 is still nicer 🙂

I played around with Dagger2, Guice and Kodein last week, and liked Kodein the most out of those 3

Hi guys, I'm trying to generate a jar file of my application and I'm facing some problems in order to put some .json files in this jar. This .json files are used as config files but every time that I try to generate the jar this .json are gone missing. Does anyone know or have any suggestion of how to solve this?

did you put them in the resources folder?

Nope

They must be in the resources folder?

if you want to package it in the jar

src/main/resources

if you're using maven/gradle

Why can't I just put this json files along with my Kotlin classes?

why not take it a step further and just do the configuration in code rather than a json file

kotlin enables such nice DSL that you could probably do it pretty easily.

How would you access it if you put it there?

The convention is to put those kind of files under

src/main/resources

if you want to package it in a jar.

a jar file is a zip file, so you can’t access the internal files like you would a normal file in your file system. Java provides an API for accessing its

resources

but you have to place those in its conventional location.

@roberto.guerra I didn't know about this convention... Thanks for the clarification 😄

Also if you have sensitive information like credentials, the recommendation is to not put those in your resources. You can either use env variables for it, or establish a location in your file system that you will access that file from.

If you want to get fancy, you can add it to your resources, but do not check it. And your build pipeline will be responsible for adding the good resource file with the sensitive information and package it and deploy.

but that is a bigger topic related to build and deployment

@trevjones We are doing this because it is a convention among the members of my team. We have stuff like database.json that stores the configs to the database across our server pipeline and stuff like en-US.json for i18n... We have been doing this kind of stuff because is the bast way that we come up with.

How could I convert something like the code down below in a Kotlin class?

{
  "default": {
    "pool": 100,
    "timeout": 10000
  },
  "development": {
    "adapter": "mysql",
    "host": "ENV['DB_HOST']",
    "port": "ENV['DB_PORT']",
    "username": "ENV['DB_USERNAME']",
    "password": "ENV['DB_PASSWORD']",
    "database": "ENV['DB_NAME']"
  },
  "staging": {
    "adapter": "mysql",
    "host": "ENV['DB_HOST']",
    "port": "ENV['DB_PORT']",
    "username": "ENV['DB_USERNAME']",
    "password": "ENV['DB_PASSWORD']",
    "database": "ENV['DB_NAME']"
  },
  "production": {
    "adapter": "mysql",
    "host": "ENV['DB_HOST']",
    "port": "ENV['DB_PORT']",
    "username": "ENV['DB_USERNAME']",
    "password": "ENV['DB_PASSWORD']",
    "database": "ENV['DB_NAME']"
  }
}

@roberto.guerra Do you have any suggestions about this situation?

I am scratching up an example of a possible option.

maybe something like this?

interface Environment {
    val adapter: String
    val host: String
    val port: Int
    val username: String
    val password: String
    val database: String
}

class EnvVarEnvironment(val keyPrefix: String) : Environment {
    override val adapter = "mysql"
    override val host = System.getenv("${keyPrefix}DB_HOST")
    override val port = System.getenv("${keyPrefix}DB_PORT").toInt()
    override val username = System.getenv("${keyPrefix}DB_USERNAME")
    override val password = System.getenv("${keyPrefix}DB_PASSWORD")
    override val database = System.getenv("${keyPrefix}DB_NAME")
}

object Development : Environment by EnvVarEnvironment("DEV_")
object Staging: Environment by EnvVarEnvironment("STAGING_")
object Production : Environment by EnvVarEnvironment("")