Open Issues Need Help
View All on GitHubAI Summary: This issue proposes changing how the system handles incompatible component layouts, specifically regarding alignment and size. Currently, such incompatibilities cause the program to crash via an assertion. The proposed solution is to replace these assertions with a mechanism that returns a user-facing error, allowing for more graceful error handling.
AI Summary: Update the project's README and example code to include documentation and usage of the `destroyEntity` function. This involves adding a description of the function's purpose and parameters to the README, and demonstrating its use within the existing `readme/main.zig` example.
AI Summary: Implement a new method, `Scheduler.eventInFlight(event: Event) bool`, in the ECEZ ECS API for Zig. This method should check if an event is currently being processed without blocking, enabling background tasks like map generation without hindering UI/rendering. Careful consideration is needed to avoid race conditions and other potential bugs.
AI Summary: The task is to modify the `getComponent` function in the ECEZ Zig ECS library to return an optional value instead of potentially panicking. This change would improve safety by explicitly handling cases where a component might not exist on an entity, preventing runtime crashes. The `getComponents` function might also require similar adjustments for consistency.