yeah. I mean you still have to make the conscious decision as a developer to use

ui

but it's not that bad

yeah, after thinking about this, I think there's no escaping having to explicitly deal with it (other than some dynamic proxy magic which I dont' want to go to)

so the goal kind of becomes - what's the least ugly, least hassle syntax I can come up with for this

and what I like about it, is that it kind of becomes like your

synchronize

block

it's a section of the code where we update UI

and if we adapt it, it can become pretty easy to spot during code reviews where someone is updating a view outside of the

ui

block

so unless anyone has any better idea, I think that's it. I'll run it past my team tomorrow, see how they like it

thanks @uhe for your help and the discussion 🙂

Hi!

How come constants in inner classes do not retain their values?

meanwhile outright hardcoding them works fine.

I have upgraded my example project with latest dependencies https://github.com/damianpetla/kotlin-dagger-example/blob/master/app/build.gradle I wonder if there is something still outdated or redundant

hey anyone having experience with retrofit base url changing at runtime? I have a issue that dagger is building the retrofit object but baseurl could change at some other time I know that there is an interceptor,but then I get stuck with

unexpected host:

why not to use several retrofit adapters?

@mingkang I'm using retrofit that way and I have no problems with it. seems to me your host string is not valid

yeah I found out the issue my host string was myserver/v1/blablabla only myserver is a valid host string

i've a simple (small) list of a Foos that i need to save out. they only contain a couple strings and a joda DateTime. what's the most straightforward way in android?

You can use Java serialization but it has caveats: ProGuard will most likely mess it up, it's not the fastest, something that I forgot

Is this for a temporary store or permanent? There are many ways including writing to file, database, serialization (don’t do that), parcelables, etc.

permanent

it's something trivial data so i don't want to put a lot of work into it

sounds like android doesn't have much between "you can store a string" to "database all the things!"

You could just serialize to JSON, and store to a file. Or to shared preferences, if it isn't very big

it's small

probably like 10 items on average, each item as i said, only have DateTime and like 2 strings

I think I saw some library that saved json in shared preferences

you could also store it all in one string in shared prefs

gson tostring

Yup. Gson works just fine