Docs: Inconsistency method return type this

[servinlp]

Describe the problem

As discussed in #22237 we want to documentation to be consistent with the return type when nothing is returned in a method. While working on fixing this inconsistency I came across another.

In, for example, BufferAttribute the applyMatrix3, applyMatrix4 and applyNormalMatrix methods all return this. On the other hand the copy method also returns this (code) but has a return type of BufferAttribute while then clone method also has the return type of BufferAttribute while actually constructing a new BufferAttribute (code).

My question, while i'm changing the return types to undefined when nothing is returned do we also want to fix this? (We meaning I'll do it together with the undefined return types.)
And if we want to do this, how should it be.

What I would like to propose is the usage of this when this is actually returned and only the current type (in this case BufferAttribute) when a new class is being constructed.

Love to hear everybody's opinions.

[Mugen87]

Thanks for bringing this topic up! It would be indeed good to clean up the return types.

What I would like to propose is the usage of this when this is actually returned and only the current type (in this case BufferAttribute) when a new class is being constructed.

This is also my preference 👍 .