System.Text.Json support a way to ignore/handle exceptions on serialization

[gokhanabatay]

NHibernate Reference properties may throw record not found exception on serialization.
With serialization options we could ignore this exception, please give us a way to ignore errors on serialization.

    public static class ObjectExtension
    {
        public static T DeepCopy<T>(this T value, bool throwsException = false)
        {
            if (value == null)
            {
                return value;
            }

            string json = JsonConvert.SerializeObject(value, new JsonSerializerSettings()
            {
                ContractResolver = new NHibernateContractResolver(),
                Error = (se, ev) => { ev.ErrorContext.Handled = !throwsException; }
            });

            return JsonConvert.DeserializeObject<T>(json);
        }
    }

NHibernate Proxy objects serialization how to define global or property level contract resolver?

 public class NHibernateContractResolver : CamelCasePropertyNamesContractResolver
    {
        protected override JsonContract CreateContract(Type objectType)
        {
            if (typeof(NHibernate.Proxy.INHibernateProxy).IsAssignableFrom(objectType))
            {
                return base.CreateContract(objectType.BaseType);
            }
            else
            {
                return base.CreateContract(objectType);
            }
        }
    }

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[gokhanabatay]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
Hi I don't have write-permissions
area-System.Text.Json

[layomia]

It seems like you want a way to try/catch exceptions when the serializer calls property/field getters on serialization:

• Should this error ignoring mechanism also be used when calling setters and object constructors? Is a way to specify which member types to include desired?
• Should the option be global (across the entire object graph), per type, or per property/field/ctor?
• Is a mechanism to produce all the exceptions encountered per (de)serialization desired?

[gokhanabatay]

Hi @layomia Newtonsoft impl. gives us an option: if an exception occurs during serialization/deserialization "field/property" "ctor"(not sure but probably) ignore exception and continue serialization/deserialization on next member.
Yes it should be global if we set "ev.ErrorContext.Handled = true" per type/property/field in that serialization.
It's a Serialization/Deserialization option that you can on/off per serialization call as you desired.

[omidkrad]

At least need a serializer option to ignore property on exception, or set it to undefined. Sometimes can get a property only when a dependent property has a certain value, otherwise it throws exception. And the object comes from a library that I cannot modify so need a way to handle it. Newtonsoft handles this gracefully.

[eiriktsarpalis]

Duplicate of #38049