ecs-component-validator

To validate ECS component usage, check that components implement the Component trait and ensure storage access is handled via query APIs rather than direct storage calls to prevent common architectural violations.

Correct ECS storage access requires using the query API exclusively. Direct storage calls bypass system execution order checks and entity destruction cleanup, leading to data inconsistency and runtime errors.

Debug ECS system registration by validating system execution order and ensuring entities undergo proper destruction cleanup. Check that new systems follow the framework's query-based access patterns to isolate registration conflicts.

Yes, the validator specifically targets Katla's ECS framework, checking component trait implementation and query correctness across katla_app and katla_ecs modules to identify storage pattern violations and provide remediation guidance.

ECS component validation fails when components lack derive(Component) or proper impl Component usage. The validator detects these missing implementations and identifies incorrect direct storage access during system registration.

Run an ECS pattern validator when adding new components or systems and when debugging ECS issues. It enforces query-based storage access and checks entity destruction cleanup to maintain architectural integrity.