Hello
I’m just playing around with PlayCanvas and declaring the types in TypeScript while I’m at it. I noticed some inconsistencies with the API that do not match with the actual playcanvas engine. Below is a list of inconsistencies and incomplete classes according to my opinion. I’ll add to the sources list if I find any others in the coming days.
Would you consider updating the API please
Thanks in advance.
Kind regards.
-J
Sources:
- Picker | PlayCanvas API Reference prepare method refers to a not documented class pc.Camera
- https://api.playcanvas.com/classes/Engine.Camera.html is referred to by pc.Picker
- AnimationComponentSystem | PlayCanvas API Reference
- CameraComponentSystem | PlayCanvas API Reference
- CollisionComponentSystem | PlayCanvas API Reference
- ComponentSystem | PlayCanvas API Reference
- ElementComponentSystem | PlayCanvas API Reference
- AudioListenerComponentSystem | PlayCanvas API Reference
- https://api.playcanvas.com/classes/Engine.AudioSourceComponentSystem.html
- ModelComponentSystem | PlayCanvas API Reference
- https://api.playcanvas.com/classes/Engine.ParticleComponentComponentSystem.html
- ScreenComponentSystem | PlayCanvas API Reference
- ScriptComponentSystem | PlayCanvas API Reference
- https://api.playcanvas.com/classes/Engine.ZoneComponentSystem.html
- MouseEvent | PlayCanvas API Reference refers to pc.MOUSEBUTTON which does not exist
- MeshInstance | PlayCanvas API Reference The “node” property of pc.MeshInstance (retrieved by pc.Picker its getSelection(x,y)) does not start with an underscore and isn’t documented in pc.MeshInstance