-
Notifications
You must be signed in to change notification settings - Fork 1
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
Support mappers #15
Comments
Check how ODMantic has solved it |
Also remove the skip of the |
I've started working on the |
Check how ormar has solved it |
lyz-code
pushed a commit
to lyz-code/clinv
that referenced
this issue
Oct 13, 2022
Until lyz-code/repository-orm#15 is fixed we can't.
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
It would be nice if the repositories could load a schema to understand the relationship between entities.
In this schema we could define the following relationships:
In a way that when we
.get
an object we get the option to load the mappers, and if they are, the repo will get the required objects and load them in the specified attribute.Possible Solution
At repo initialization, a
schema
attribute is set with the desired relationships.Then we will need to decide how it affects the different base methods.
Additional context
Related Issue
The text was updated successfully, but these errors were encountered: