-
Notifications
You must be signed in to change notification settings - Fork 12
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
Namespace and type naming collisions #26
Comments
I think renaming the What about prefixing the entity names? Something like We can probably then leave the namespaces the same. |
I do like prefixing the entity names, but you would still have a conflict with the namespace and the Terraria entity. Since the concrete types are going into TShock, we would name them Also, something to note is that our type names conflicting with Terraria names shouldn't make too much of a difference in our name decisions, since our goal is to eventually have consumers not need to reference anything in the Terraria namespace. |
Prefixing them with Note: Ignore accidental comment+close |
If there are no objections to the namespace renaming, then I will do this tonight. |
Please detail the exact changes you'll make, for the sake of having it on record+everyone being on the same page. |
EDIT: where |
There are a few instances of shared namespace and type names:
class Orion
and namespaceOrion
class Item
and namespacesOrion.Entities.Item
,Orion.Events.Item
class Npc
and namespacesOrion.Entities.Npc
,Orion.Events.Npc
class Player
and namespacesOrion.Entities.Player
,Orion.Events.Player
class Projectile
and namespacesOrion.Entities.Projectile
,Orion.Events.Projectile
This could lead to a few annoyances later on, and should probably be fixed now. One solution would be to pluralize
Orion.Entities.<EntityName>
(and place the events in there too, or pluralize that as well). I'm not sure how we should deal withOrion.Orion
, though.The text was updated successfully, but these errors were encountered: