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

Feature dataclass #34

Open
gzt5142 opened this issue Apr 20, 2023 · 0 comments
Open

Feature dataclass #34

gzt5142 opened this issue Apr 20, 2023 · 0 comments

Comments

@gzt5142
Copy link
Owner

gzt5142 commented Apr 20, 2023

Recommend to invert the dependency relationship between a "Feature" object and the ORM implementation of that object. Would rather have the ORM depend on the model rather than the other way around (as it is now).

While I don't think it makes sense to abstract away the implementation completely, I think it will be helpful to reduce coupling with the ORM for most of the business logic.

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

No branches or pull requests

1 participant