You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 1, 2022. It is now read-only.
Thx for sharing (I guess I may close this now), though actually I decided to write my own ECS implementation, and ended up with components being simple js objects, while the rest classes like Entity, System, World, - they're all replaced with different implementation having similar API. I wrote a couple posts about it here:
I honestly don't see any reasons why components should be classes, when it's basically data and doesn't (shouldn't) have any logic implementation. In my second article I feature how GPU usage / CPU usage / FPS, - all improved due to all my changes. Schemas and queries gone down to attribute access, and overall types are more straightforward.
I have this simplest ECSY component written in TypeScript:
And I have further error:
I initially thought it's component's schema, and tried doing this:
But later on upon using this, I faced further error:
From component definition I don't quite understand: what is this? Here's its definition:
What is this
C
?And how do I deal with this
Property 'primitive' does not exist on type 'Readonly<Component<any>>'
error?The text was updated successfully, but these errors were encountered: