Reason for <arrowHelper /> not accepting arguments as arrays?

[Amar-Gill]

Here is the repro I made for this issue: https://codesandbox.io/s/affectionate-brattain-wr9zi?file=/src/App.js (you will have to zoom way in to see the objects)

I was wondering why for the <arrowHelper /> constructor, I can't pass in Vector3 arguments as arrays into the args array, as is the case for other properties.

         const dir = new Vector3(0, 1, 0);
         dir.normalize();
         const origin = new Vector3(0, 0, 0);
         const length = 2;

       ...............

        // doesn't work
        <arrowHelper args={[[0, 1, 0], [0, 0, 0], 2, "black"]} />

        // works
        <arrowHelper args={[dir, origin, length, "black"]} position={[2, 0, 0]} />

[Amar-Gill]

Also, let's say I want to include the arrow helper in a <group> (I'm visualizing vectors for my project), and I want to do some animations on the <group>, will it hinder performance if I pass in Vector3 as args into the constructor? The props that will be changing are position and rotation.

[drcmda]

These are constructor arguments, it expects a vec3 according to the documentation. If any of it is stored internally as this.direction or whatever you can use prop short notation.

Also, if anything changes inside ARGS, the object is reconstructed from scratch. Essentially it's the same as: new Foo(arg1, arg2, ...)

[Amar-Gill]

OK I understand now. The direction and origin properties do not have set methods. I don't have to worry about reconstructing them because I am only changing position and maybe rotation, which are exposed via shorthand notation.

[drcmda]

when i see something like that and im sure im going to re-use it, i usually create a component that abstracts the pesky imperative stuff.