Add namespaces for components and systems for easier file structure#88
Open
W3NDO wants to merge 2 commits intoecsx-framework:masterfrom
Open
Add namespaces for components and systems for easier file structure#88W3NDO wants to merge 2 commits intoecsx-framework:masterfrom
W3NDO wants to merge 2 commits intoecsx-framework:masterfrom
Conversation
- Added a namespace flag for easier organisation of components and systems
- fixed formatting
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When using ecsx, entities are entirely conceptual. I however struggle with keeping everything in my head as the number of components or systems grow. This pull request adds a flag on the systems and components generator
--namespacethat allows creating the associated files in specific namespaces.For instance, If we have a game simulation where we have a ship entity(conceptual) with XPosition, YPosition, HealthPoints and Armor components, we could run
and end up with this folder structure:
I have added tests to ensure that the components and systems are correctly added to the
manager.exand that the files are correctly generated. Similarly the file content is updated accordingly so that a file likehealth_points.exwill contain: