Proposal: Importing STEP assemblies as nested layers, not nested blocks

[eobet]

I just posted this question:

Script that explodes & renames all blocks with only 1 object?

Has anyone made such a thing? I find that when I import STEP files, even single objects with only 1 instance become blocks, which I find unnecessary, but when you explode them, you lose the object name (because the body name is usually unnamed or just have a generic surface/feature name).

…so I hope that any future implementation of blocks to layers will take this into account and never produce a layer with only one object in it (it could be an option, I guess, for those who want a nightmare of a file to manage, hehe).

Btw, is there any chance of a solution regarding instanced objects with layers? Can’t remember if this was discussed or not.

(PS. I now found a script by @Pascal that enables me to move BlockDefinitions which was the root cause of all of this, so yeah… if the editing/managing of Blocks in Rhino would have been modernized, as suggested here in 2015, this whole ordeal could have been avoided.)