-
Notifications
You must be signed in to change notification settings - Fork 22
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
Add more examples #14
Comments
I think an example of mapping QuerySpecs when we are doing the DTO mapping with MapStruct would be very useful. |
I just found mapstruct/mapstruct#702 (comment) |
sounds good to me. You already have something running? or still in immediate need of an example? |
unfortuatenly nothing automatic as of yet. But there is a QuerySpecMutator class that can help getting the job done. |
I should be able to provide something using I have to admit I'm having hard time with the last point (JPA relationship example). I will try to explain what I'm trying to do. DTO -> Crnk Repository -> MapStruct -> Entity -> DAO (and the other way around for the response). I can manage it with a regular repository but for the relationships I'm not sure how to approach it. I'm currently trying with |
I'm making some progress. The only major missing part is QuerySpec translation. Where can I find the |
a sorry it is `QuerySpecVisitor` rather than `QuerySpecMuator`. It can then
be used with `QuerySpec.accept`
Am Mi., 30. Okt. 2019 um 14:33 Uhr schrieb Christian Gendreau <
[email protected]>:
… I'm making some progress. The only major missing part is QuerySpec
translation. Where can I find the QuerySpecMutator class?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#14?email_source=notifications&email_token=AB5DJFKV5XK6M5XN6C7YKJ3QRGEJDA5CNFSM4FBW2HR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECUFY6Y#issuecomment-547904635>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB5DJFPZ42MOQY4XCMMX5ITQRGEJDANCNFSM4FBW2HRQ>
.
|
The text was updated successfully, but these errors were encountered: