The main issue is that, if the objects created by schema builder are not complete enough, they can cause problems down the line. Imagine a clash detection script, it would massively fail if the walls sent only have a baseline instead of a 3d mesh representation.
We had various feedback on this issue in v1 as a matter of fact.
I think Speckle should create Objects, only when it can properly set their main properties, otherwise it should be “attaching the schema” so that when receiving in a BIM software these are properly created.
As a matter of fact, the original Schema Builder component was created as a hack to create BIM objects in Revit from GH, if was never really meant to be a tool to create full BIM objects.
I understand this is not the case for most of the 2D structural elements @daviddekoning , which are simple to generate and can be used “as they are” in various scenarios. This is why we ultimately think that a fair compromise is leaving the choice to the user, whether to attach or create.
Alternatively, we could add an attribute to the Objects’ class definnitions to specify a default behaviour (eg create for 2d objects, and attach for all others), but this could confuse the users even more…