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
Regarding the issue #2540 i found out that we often use two json serializers: Newtonsoft.Json and System.Text.Json.
Because of that we always need to add two attribute classes when defining custom property naming for serialization/deserialization. E.g.: [JsonProperty("sid"), JsonPropertyName("sid")]
@abarz722 & @tpurschke do you see any potential caveats im missing? The RestSharp Rest Client is using it's own namespace for the serializers...
I would go for System.Text.Json package because this is no extra package and directly maintained by MS. But System.Text.Json offers fewer flexibility that we might need. If yes, we go for Newtonsoft
The text was updated successfully, but these errors were encountered:
@NilsPur says: class System.Text.Json.Serialization can be removed
best to auto-remove all JsonPropertyName occurances in our code using regular expressions
@NilsPur says: class System.Text.Json.Serialization can be removed best to auto-remove all JsonPropertyName occurances in our code using regular expressions
Regarding the issue #2540 i found out that we often use two json serializers: Newtonsoft.Json and System.Text.Json.
Because of that we always need to add two attribute classes when defining custom property naming for serialization/deserialization. E.g.:
[JsonProperty("sid"), JsonPropertyName("sid")]
@abarz722 & @tpurschke do you see any potential caveats im missing? The RestSharp Rest Client is using it's own namespace for the serializers...
I would go for System.Text.Json package because this is no extra package and directly maintained by MS. But System.Text.Json offers fewer flexibility that we might need. If yes, we go for Newtonsoft
The text was updated successfully, but these errors were encountered: