Unexpected UI elements interaction for collections of same type

Hello, I’ve stumbled upon a bug in UI elements where collections expand as a group, despite being on different objects. I’m using graph view in this example, though this problem does not appear to be related to stemming from graph view.

I’ve confimed that the scriptable objects for each node have a different instance ID. You can also see on the embedded video that they are distinctly different UI elements. I should note that the other shared field do not edit together and I can add/remove items from the lists independently. This is strictly a bug with the expansion/closure of list views.

A snippet of the scriptable object code, it’s just an ordinary list as shown here:

public class NodeEditorData : ScriptableObject
{
    [SerializeField]
    public List<NodeLink> links = new List<NodeLink>();
}

blueharshdoctorfish

Can you share some code that could help us reproduce the issue?