that is really nice... just changed.... thanks again...

Great! Back to bed for me 🙂

good night...

Good night, John.

I think I already use that syntax

I'll check when I am near a computer

@User uploaded a file: Untitled

yup I do in keepassFX

allthough I see that I did not change the lists

I love that new syntax. Much easier to read.

I should check if it works with the

LocalDateTime

I cant wait to finish this puppet migration and have my head cleared again

@ron It should 🙂

I will try to submit a talk to KotlinConf tonight as well 🙂

Let's say I have a domain object

Project

locally and and a

Project

object remotly which can by updated via Rest. Locally I have a

ItemViewModel

called

ProjectModel

I want that all changes will be automatially be synced. My idea was to inject my

rest controller

int the

ProjectModel

and override the

commit

function. The

commit

function will call the

super.commit(...)

and call the

rest-api

to sync the remote object... is this the right way to to it?

Oky just realized that commit is not open so my approach would not work 🙈

@nimakro You can do that by overriding the

onCommit

callback on

ViewModel

. I've never done it that way, but I don't think there is anything wrong with that approach.

@edvin Well the problem with

onCommit

is that I don't know which properties changed since I would like to only send the changed properties, so how are you usually doing something like that if you don't use the

ViewModel

?

@nimakro I always submit the whole model over Rest, I don't need to save bytes 🙂 But let me see what I can do about that, hang on.

@edvin Well I could probably do that as well, I just thought the api is supporting it so why not use it but I am not sure it that is an overkill anyways!

@nimakro Would you simply need to know what fields changed, or also the old/new value of those fields?

@edvin It would be enough to know which fields changed with the new value.

@User uploaded a file: Optional onCommit callback with list of committed properties and their status

The

PersonModel

has three fields.

@nimakro It does more than you need, but you can get only the changed committed fields by doing

commits.filter { it.changed }

.

@edvin Awesome, that looks good and thanks for your help, I will update the docs tonight..

@nimakro Thank you for always doing that. I really appreciate it.

@edvin No problem and thanks for your great work!!

My pleasure. That was a nice use case for this feature.

@User uploaded a file: Untitled and commented: @edvin This is how I am using the

onCommit

now