You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Constructor detection on deserialization only works when all the arguments in the ctor are of a simple type (more specifically, of a type present in the Reflection.ConvertType dictionary).
In the example below, if the DateTimeOffset parameter is removed, the code works as expected.
Version
LiteDB v5.0.8, .NET Core 3.1
Describe the bug
Constructor detection on deserialization only works when all the arguments in the ctor are of a simple type (more specifically, of a type present in the
Reflection.ConvertType
dictionary).In the example below, if the
DateTimeOffset
parameter is removed, the code works as expected.Code to Reproduce
Expected behavior
Deserialization with custom ctor working for any parameter type.
Additional context
This is very important for compatibility with C# 9 positional records.
The text was updated successfully, but these errors were encountered: