-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
organize under single health
package
#71
Comments
Totally agree! While we're at it, can we sort and organize the events and components in this module as well? 🙃 I think putting modules into a dedicated |
Following the same pattern as proposed in Terasology/Inventory#37 I suggest the following structure:
|
this is really opening the can of worms, but do you want to change any of those class names while we're at it? the thing that made me ask is looking at those events and seeing things like
|
Yes, I do 💍 😅 |
Organizes everything in this module under the namespace `org.terasology.module.health`. Sub-packages are used to organize the elements of the ECS, namely: - components - systems - events - ui BREAKING CHANGE: moving and renaming packages is incompatible for all modules depending on Health. Resolves #71
Organizes everything in this module under the namespace `org.terasology.module.health`. Sub-packages are used to organize the elements of the ECS, namely: - components - systems - events - ui BREAKING CHANGE: moving and renaming packages is incompatible for all modules depending on Health. Resolves #71
The package names currently used in this module make it difficult to distinguish which classes are in this module and which are from engine or elsewhere.
Recommend all packages here descend from a single
org.terasology.health
(ororg.terasology.module.health
?) instead oforg.terasology.logic
&rendering
.The text was updated successfully, but these errors were encountered: