Expose Node3D.scale() as scale_object()

[Muller-Castro]

Expose Node3D.scale() to the editor side as scale_object().

[AThousandShips]

This isn't valid, you can't expose scale because there's already the scale property

[Muller-Castro]

This isn't valid, you can't expose scale because there's already the scale property

Can this be exposed under another name?

[AThousandShips]

Sure, unsure what name would be appropriate though

Also unsure if we should have a whole three different scaling methods, we already have global_scale and scale_object_local

[Muller-Castro]

If I haven't tested it wrong, this method scales along the local axes of the parent node so it's different from the other two.

[Muller-Castro]

Here's the difference:

[AThousandShips]

Right, it's different, I'm saying it'll be confusing with three different ones

[Muller-Castro]

It'd pair with rotation methods as there are 3 different types rotate_object_local, rotate and global_rotate.

In the end this is just a shortcut for transform.basis = transform.basis.scaled(Vector3(x, y, z))

[Muller-Castro]

Sorry I'm confused. Should I close this PR or change the exposed name?

[AThousandShips]

Go ahead and change it and we'll see what name is agreed on

Discussed

[fire]

We resolved the name overlap so I think the scale_object gdscript expose is fine.

[AThousandShips]

Let's add the details for this one in #87440

[Mickeon]

Commit & PR could use a better title since the name has changed

[Muller-Castro]

Such as "Expose Node3D.scale() as scale_object()" ?

[Mickeon]

Yes, sounds fine enough

[Mickeon]

Docs are consistent and just fine, if this review is of any additional support.