Circular dependencies detection problem 2

Continuation of https://github.com/ExtendedXmlSerializer/home/issues/583

I have new case of same problem Looks like this problem have more shades. Problem found unexpectedly, previously we use .EnableReferences() but soon as we switched to .AllowMultipleReferences() new problem is occured. If I EnableReferences for same object it will serialize successfully, but will never use exs:reference="1"exs:identity=“1” I suppose this object should serialize with .AllowMultipleReferences only Even Array.Empty<string> will be detected as MultipleReferences

using ExtendedXmlSerializer;
using ExtendedXmlSerializer.Configuration;

var sameInnerObject = new InnerObject { Id = 100, Items = new string[] { } };
var testRootObject = new RootObject
{
    Item1 = sameInnerObject,
    Item2 = new InnerObject2 { Items = sameInnerObject.Items },
    List = new List<InnerObject>()
};

IExtendedXmlSerializer serializer = new ConfigurationContainer()
    .AllowMultipleReferences()
//.EnableReferences() 
    .Create();
var serialized = serializer.Serialize(testRootObject);
Console.WriteLine("Success");

public class RootObject
{
    public InnerObject Item1 { get; set; }
    public InnerObject2 Item2 { get; set; }
    public List<InnerObject> List { get; set; } = new();
}

public class InnerObject
{
    public int Id { get; set; }
    public string[] Items { get; set; }
}

public class InnerObject2
{
    public string[] Items { get; set; }
}

[UladimirLameyko]

@Mike-E-angelo Look like it helps on my side. Currently it is not generating Exceptions. Thanks. Please push it into nuget😎

[Mike-E-angelo]

Oh I see… are you saying this is throwing a CircularReferencesDetectedException instead of a MultipleReferencesDetectedException? I can look into that if so. 👍