three.js: BufferGeometry: .setIndex method does not take null as input

I just want to add a note on the fact the setIndex implementation might already accept null as input, it’s only the TypeScript definition that lacks this input type.

Then feel free to enhance the respective TS declaration file if this solves your original issue 👍

For me it’s mostly an API consistency and ergonomics issue… if the following code is valid:

var geometry = new BufferGeometry();
geometry.setAttribute( 'position', positionAttribute );

// index is null.
geometry.setIndex( index );
// index is not null.

… then we are allowing users to incrementally construct BufferGeometry instances with “invalid” intermediate states, and as long as the state is valid when rendering, that’s fine. For the reverse — removing an index — not to work feels like a surprising “gotcha” in the API. Patterns exist for immutable objects (Builder patterns, or requiring immutable properties as constructor arguments) but irreversible setters are unusual.

I can contrive some use cases…

• declarative frameworks like react-three-fiber or A-Frame might want to clear properties in one method and set the new values in another
• user might use multiple indexes as more flexible draw ranges on a “triangle soup” mesh, or remove that index to draw the entire mesh

… but IMO the priority is “what is least likely to surprise the developer” here.

Um, I did not think of deleteIndex() so far. But I really like it^^.

Yes, I simply expect my users to know what they are doing. So if they change the index, they must change the vertices.