api/client/metrics return 400 when using System.Text.Json for seriaization. about unleash-client-dotnet HOT 5 CLOSED

Thank you @erandjo for raising this. We'll have a look! Interesting though, I'd have thought providing Naming policy camel case through JsonSerializerOptions would have sorted this

from unleash-client-dotnet.

where I found that dependencies was optional and defaulting to an empty lists of dependencies (similar to the issue you shared). Is this the reason why dependent features wont work when using System.Text.Json, and will this also be true for variants?

Hello @erandjo! No, it's inside dependency implementation. Spec requires enabled to default to true if not set in the JSON payload, and we didn't want to expose a nullable boolean on the dependency itself, leading to System.Text.Json not being able to resolve the type/property/parameter since once is a bool? and the other a regular bool. Ends up with runtime deserialization errors. (dotnet/runtime#44428)

Docs on dependent features is here by the way: https://docs.getunleash.io/reference/dependent-features

from unleash-client-dotnet.

Couple of things here

1. For serialization use also camel case options
2. Setting stream position to 0 in the end of serialization

Although, this will eventually not work with Dependent Features, because of an issue in .NET runtime dotnet/runtime#44428

class TextJsonSerializer : IJsonSerializer
{
    private readonly JsonSerializerOptions options;

    public TextJsonSerializer()
    {
        options = new JsonSerializerOptions
        {
            PropertyNamingPolicy = JsonNamingPolicy.CamelCase,
        };
    }

    T IJsonSerializer.Deserialize<T>(Stream stream)
    {
        var instance = JsonSerializer.Deserialize<T>(stream, options);
        if (instance == null)
        {
            throw new Exception("The result of serializing feature toggle is null");
        }
        return instance;
    }

    void IJsonSerializer.Serialize<T>(Stream stream, T instance)
    {
        JsonSerializer.Serialize(stream, instance, options);
        stream.Position  = 0;
    }
}

from unleash-client-dotnet.

Wow. thank you. This seems to be a blunder on my part, forgetting to pass in options; I am sorry about that. I will close the the issue. Interesting side note about dependent features. Thanks again.

from unleash-client-dotnet.

I searched for dependent features on unleash and unleash dotnet sdk out of curiosity for what you meant with the comment about dependent features not working in the future. I couldnt find an exact reference to dependent features (with exception of some tests).

These tests lead me to the FeatureToggle constructor:

        public FeatureToggle(string name, string type, bool enabled, bool impressionData, List<ActivationStrategy> strategies, List<VariantDefinition> variants = null, List<Dependency> dependencies = null)
        {
            Name = name;
            Type = type;
            Enabled = enabled;
            ImpressionData = impressionData;
            Strategies = strategies ?? new List<ActivationStrategy>();
            Variants = variants ?? new List<VariantDefinition>();
            Dependencies = dependencies ?? new List<Dependency>();
        }

where I found that dependencies was optional and defaulting to an empty lists of dependencies (similar to the issue you shared). Is this the reason why dependent features wont work when using System.Text.Json, and will this also be true for variants?

from unleash-client-dotnet.