fix IL trimming warnings

[Stepami]

Using JsonSerializer.Serialize{TValue}(TValue, JsonTypeInfo{TValue}) overload to avoid IL warnings

Info:

• Validly 1.1.5

Still have trouble publishing AOT:

    ILC : Trim analysis warning IL2026: Validly.ValidationMessage.<>c.<.ctor>b__0_0(Object): Using member 'System.Text.Json.JsonSerializer.Serialize<Object>(Object,JsonSerializerOptions)' which has 'RequiresUnreferencedCodeAttribute' can break functionality when trimming application code. JSON serialization and deserialization might require types that cannot be statically analyzed. Use the overload that takes a JsonTypeInfo or JsonSerializerContext, or make sure all of the required types are preserved.
    ILC : AOT analysis warning IL3050: Validly.ValidationMessage.<>c.<.ctor>b__0_0(Object): Using member 'System.Text.Json.JsonSerializer.Serialize<Object>(Object,JsonSerializerOptions)' which has 'RequiresDynamicCodeAttribute' can break functionality when AOT compiling. JSON serialization and deserialization might require types that cannot be statically analyzed and might need runtime code generation. Use System.Text.Json source generation for native AOT applications.

[Stepami]

@Hookyns what is package version update strategy now?

[Hookyns]

I'd like to run some tests related to this. For now, I published it as 1.1.6-rc.1

[Stepami]

@Hookyns any updates?

[Hookyns]

I'd like to do that this weekend. I also want to update the documentation - especially, to document the ASP.NET Core extension.

[Stepami]

@Hookyns have you succeeded in running some tests?
Having IL warnings absent in release nuget would be really great!

[Hookyns]

@Stepami do you use Validly with AOT, and does it work for you? I’m concerned it cannot work because the <IsAotCompatible Condition="$([MSBuild]::IsTargetFrameworkCompatible('$(TargetFramework)', 'net7.0'))">true</IsAotCompatible> condition is always false. This happens since it targets netstandard2.0, which is not considered compatible with net7.0 (the check returns false).

I’ll add all the new AOT-compatible targets (net7.0; net8.0; net9.0; net10.0), so that should resolve the issue. Hopefully, this will show some noticeable improvement in the benchmark.

EDIT:

<PropertyGroup>
    <ValueAotCompatible>$([MSBuild]::IsTargetFrameworkCompatible('$(TargetFramework)', 'net7.0'))</ValueAotCompatible>
</PropertyGroup>
<Target Name="BuildInfo" AfterTargets="Build">
    <Message Text="$(TargetFramework) is AOT compatible: $(ValueAotCompatible)" />
</Target>

BuildInfo:
         netstandard2.0 is AOT compatible: False
         net10.0 is AOT compatible: True
         net7.0 is AOT compatible: True
         net8.0 is AOT compatible: True
         net9.0 is AOT compatible: True

[Stepami]

@Hookyns i do, but IL trimming warnings must be absent

[Stepami]

@Hookyns hi!
Will this PR be merged?

Can't use the lib in my projects because of the wrong STJ API call under the hood in 1.1.5.

Really need this fix 🙏