-
Notifications
You must be signed in to change notification settings - Fork 56
Update Javadoc when setting custom attributes for users. #53
Conversation
I think we should add in that runtime check / logging we discussed as part of this PR. |
…ibute. Fix formatting. Fix null check in user builder.
@@ -0,0 +1,14 @@ | |||
package com.launchdarkly.client; | |||
|
|||
public enum UserAttribute { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this should have package level access.
👍 after changing the visibility of the new enum. |
* @param k the key for the custom attribute | ||
* Add a {@link java.lang.String}-valued custom attribute. | ||
* | ||
* @param k the key for the custom attribute. When set to one of the built-in user attribute keys, this custom attribute will be ignored. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps consider referencing the documentation directly on which keys are considered "built-in" (http://docs.launchdarkly.com/docs/targeting-users#targeting-based-on-user-attributes)?
Given that UserAttribute
is package private it would be good to have an explicit reference to all attributes are considered "built in".
Yes-- let's reference the documentation here. |
…itted manual test file.
…-attrs avoid throw/catch when evaluating user attributes
Update Javadoc when setting custom attributes for users.