-
Notifications
You must be signed in to change notification settings - Fork 28
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
Overlap with Railways #32
Comments
My plan is to get to a point where I have a class representing a EntityType and a few implementations that do things like implement Where functionality is different based on the type of entity, that logic is contained in the implementation for that group of entities.
|
If rails are the only ones that have this issue, however, maybe it would be a better idea to add a |
This is looking awesome! Only major thing I noticed is that Also, I might be confused on how this works but: x(x) {
if (!this.position) this.position = new Victor({x: 0, y: 0});
if (!x) return this.position.x;
this.position.x = x;
return this;
} Why might position not be defined if it's defined as a function just above? And how come you're using |
It's most certainly work in progress. The first point is certainly a bug and I've changed it to if (typeof value === 'undefined') return this[name]; The second is also a bug and the property should be In const Entity = require('./entity')(entityData); with const Entity = require('./entitycompat')(entityData); to run the tests against my replacement implementation. |
Railways are hard!
I'm looking at improving this as some of my projects also include rails.
The text was updated successfully, but these errors were encountered: