Bugfix for deserializing nullable enum properties.

[adambarath]

Scenario of:

    enum SomethingEnum { A, B, C }

    class TestOfNullableEnums
    {
        public SomethingEnum? TestEnumNullable { get; set; } // Nullable<SomethingEnum>
        public SomethingEnum TestEnum { get; set; }

        public int Id { get; set; } // placeholder
    }

The table definition would be INTEGER for TestEnumNullable property and TEXT for TestEnum property. And table API data could not be deseralized on client side and stored in SQLite of:

 ..[ ... {  "testEnumNullable": null, "testEnum": "B", ...  } .. ].. 

[adrianhall]

Love it! A quick code review suggests it is solid code.

Can you please add a test for this. Best way is probably to add something into the Integration tests for KitchenSink.

[adambarath]

Tried my best.

After adding nullable enums to models and removing my fix some test were break. It was great to see that my fix works pretty weel on unit test side as well. :)

[adrianhall]

Thanks - I'll take a look at the tests on Friday and see what we can do.

[adrianhall]

Made one change - swapping Type instead of Type?, since the #nullable context is disabled in StdLibExtensions.cs.