recordUserDetails should have it's counterpart to safely update custom properties

[delebedev]

SDK should allow to query current user details
- (NSDictionary *)currentUserDetails

Use case for that:

1. I'm setting custom property on user upon initialization:
   [[Countly sharedInstance] recordUserDetails:@{kCLYUserCustom: @{@"prop": @1}}]
2. Then in completely different part of the app I want to set another property:
   [[Countly sharedInstance] recordUserDetails:@{kCLYUserCustom: @{@"prop2": @"another"}}]

Which apparently wipes my first property.

Proposed approach is to query currentUserDetails and update this collection as necessary, then perform
[[Countly sharedInstance] recordUserDetails:adjustedUserDetails]

Another possible solution is to iterate kCLYUserCustom inside SDK and update keys in the same fashion as predefined keys (e.g. name or birthday) -- checking if they are non-nil before updating.

Would be happy to make PR, just let me know what approach is preferred.

[erkanyildiz]

Hello,

I will make sure the new SDK follows these new rules about user details soon:
http://resources.count.ly/docs/sdk-development-guide#section-user-details

push and pushUnique methods on pseudo code should be ok, right?

[delebedev]

@erkanyildiz Documentation still looks not very obvious for me, sorry. Just to confirm:

Countly.userData.push(string key, string value) is going to append user properties to existing value of the property and form an array
Countly.userData.pushUnique(string key, string value) is going to replace particular user property

is that correct?

[ar2rsawseen]

@garnett those two methods you listed will be used for custom properties and they will create an array property with many possible values, in first situation with possible duplicatevalues in second only with unique values

[delebedev]

I see, thanks @ar2rsawseen. Is there any approximate estimation of rolling this changes out?

[erkanyildiz]

We can say within this month.

[erkanyildiz]

This commit solves it: f2ac81f

Soon we will merge.