You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to inherit the methods / properties on a Model, one has to "create" one then inherit from it's prototype. This seems inefficient and unnecessary. Perhaps a separate module for models would enable inheritance as well as contribution back to the set of models.
The text was updated successfully, but these errors were encountered:
Sure, I imagine that will add some flexibility to the design. So long as the public interface for all models is pretty clear (e.g., minimum number of methods that need to be implemented to be considered a valid model).
In order to inherit the methods / properties on a Model, one has to "create" one then inherit from it's prototype. This seems inefficient and unnecessary. Perhaps a separate module for models would enable inheritance as well as contribution back to the set of models.
The text was updated successfully, but these errors were encountered: