I think the merge POP should allow for a definition of how to handle attributes that are defined in multiple inputs but as different classes. E.g. merging a default sphere with a default box results in an object that has both point and vertex normals, where each covers only part of the full geo. I see how this should potentially be the default behavior. But I’d ask for an option to control how to merge these. Maybe via sequential parameters, where we can set attribute names and define what class they should be converted too.
Hello @josefpelz
Thanks for the suggestion. I’ve noted it down so the team can evaluate it. To preserve backward compatibility, the default method for handling identical attribute names will likely remain the same.