Skip to content
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

Use Abstract models and interfaces instead of optional configurable models #23

Open
gerardojbaez opened this issue Nov 18, 2017 · 0 comments
Milestone

Comments

@gerardojbaez
Copy link
Owner

Will be a better approach to use abstract model classes and model interfaces instead of using real models in the package. This will force the developer to implement their own models that extends and implements the base abstract class.

This is helpful in cases where the developer wants to apply different logics to each model. A good example is the Plan model, for multilingual applications, this model needs to be translated.

The current approach works, but IMHO this new alternative is a better fit.

Any suggestions are welcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant