Is there a way to use some `env` values with multi...

# multiplatform

[Vitor Prado]

Is there a way to use some env values with multiplatform? I’ll try to describe my problem:
My api needs to receive some headers based on application: platform, version, language.
This info is platform-client dependent.
How can I achieve it?

[zalewski.se]

Just create expect/actual wrapper?

[Vitor Prado]

no.. expect-actual is for library code.. i need something to configure it in client code (the app, not the library)

[Big Chungus]

epect/actual is for anything, not just libs...

[Vitor Prado]

my lib can expose expect via swift framework lib? (I think it’s incompatible/impossible)

[Trevor Stone]

can you just expose an interface and put it as a required param in the constructor for whatever needs those values

[Trevor Stone]

or a class/data class that holds those values and then pass the constructed object in

[Vitor Prado]

@Trevor Stone is DI a good idea to expose the values?

[Javier]

Why not expect/actual?

[Trevor Stone]

It looks like you have a project that will be packaged as a library for more than one consumer

[Trevor Stone]

you need information based on which consumer is using the library at the time

[Trevor Stone]

so you will either need to build a specific library for each consumer, or you will need to have the consumer provide the information to your library

[Javier]

I think you are going to get the same thing using DI or expect/actual

[Javier]

But expect actual should be easier

[Trevor Stone]

expect/actual is provided at compile time. If you are a library that needs config based on how it is being consumed that needs to be at runtime

[Trevor Stone]

I might be misunderstanding @Vitor Prado's request, but it seems like the consumers are in a separate code-base and are the owners of the configuration

[Big Chungus]

Use expect actual to hook in native apis for each platform to load those env variables...

[Javier]

Then passing a simple data class with the data in a constructor should be enough

[Vitor Prado]

@Big Chungus good solution. thanks!

[Vitor Prado]

@Trevor Stone yeah.. you’re right.. but I think what Martynas said is a good solution. (don’t expose an object/api to client but is a simple solution)

[Big Chungus]

Bonus tip - model your expect api after one of the platforms apis. That way you can just typealias the actual on that platform

[Vitor Prado]

do you have an example?

[Big Chungus]

https://www.github.com/mpetuska/kvdom/tree/master/kvdom%2Fkvdom-dom%2Fsrc%2FjsMain%2Fkotlin%2Flt%2Fpetuska%2Fkvdom%2Fdom%2FNode.kt