Config Cat User
An object containing attributes to properly identify a given user for variation evaluation. Its only mandatory attribute is the identifier.
Custom attributes of the user for advanced targeting rule definitions (e.g. user role, subscription type, etc.)
The set of allowed attribute values depends on the comparison type of the condition which references the User Object attribute.
String values are supported by all comparison types (in some cases they need to be provided in a specific format though).
Some of the comparison types work with other types of values, as described below.
Text-based comparisons (EQUALS, IS ONE OF, etc.)
accept String values,
all other values are automatically converted to String (a warning will be logged but evaluation will continue as normal).
SemVer-based comparisons (IS ONE OF, <, >=, etc.)
accept String values containing a properly formatted, valid semver value,
all other values are considered invalid (a warning will be logged and the currently evaluated targeting rule will be skipped).
Number-based comparisons (=, <, >=, etc.)
accept Double values and all other numeric values which can safely be converted to Double
accept String values containing a properly formatted, valid Double value
all other values are considered invalid (a warning will be logged and the currently evaluated targeting rule will be skipped).
Date time-based comparisons (BEFORE / AFTER)
accept korlibs.time.DateTime values, which are automatically converted to a second-based Unix timestamp
accept Double values representing a second-based Unix timestamp and all other numeric values which can safely be converted to {@link Double}
accept String values containing a properly formatted, valid Double value
all other values are considered invalid (a warning will be logged and the currently evaluated targeting rule will be skipped).
String array-based comparisons (ARRAY CONTAINS ANY OF / ARRAY NOT CONTAINS ANY OF)
accept arrays of String
accept String values containing a valid JSON string which can be deserialized to an array of String
all other values are considered invalid (a warning will be logged and the currently evaluated targeting rule will be skipped).
In case a non-string attribute value needs to be converted to String during evaluation, it will always be done using the same format which is accepted by the comparisons.