Introduce Object and ObjectSupportedType

[ashalva]

Motivation

Currently Toggles support only primitive types, but seemingly there is some need to add support for objects. I will be working for some time to add support for objects in Toggles. So, expect some more prs in upcomings days/weeks.

Implementation

This is how the object based Toggle will be represented as json 👇

Object json

{
    "variable": "object_toggle",
    "object": {
        "boolProperty" : true,
        "stringProperty" : "value",
        "intProperty" : 420
    },
    "metadata": {
        "group": "Raw toggles",
        "description": "Object toggle"
    }
}

The basic flow for Toggles is to intake the predefined json structure and it will decode into the Toggle array. Toggle keys are predefined e.g bool, int etc. When we are talking about objects though, we need some mechanism which will allow us to use dynamic keys.

That's why I am introducing two new objects in the SDK.

Object

This is the structure which will be returned to SDK consumer at the end when they ask for object value for concrete Variable. Object gives the consumers ability to access their object ether as dictionary (map property) or decoding that map to their expected type T by calling asType<T>()

It has custom decoding strategy. We will be decoding above mentioned json to dictionary where value is actually enum ObjectSupportedType. On top of that, it throws errors in several scenarios:

1. If objects key is empty.
2. If the object is empty.
3. If the object is nested.

ObjectSupportedType

It makes sure that our Object has predefined value support. Each property must be either: Bool, Int, String or Double. It will throw an exception if it encounters other type while decoding.

Tests

Tests are covering 100% of the new code.

[albertodebortoli]

Thanks @ashalva 🙌 Looking good!

[AlexLotsu]

Could some additional tests be added?

You could consider tests for this new type in Value+UtilitiesTests, Value+AccessorsTests, Dictionary+TogglesTests

[ashalva]

You could consider tests for this new type in Value+UtilitiesTests, Value+AccessorsTests, Dictionary+TogglesTests

Thanks @AlexL271828, every part of the new code is tested but in one file. 100% of the new code is covered with unit tests.