nested relations query #28
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1. `join` can be set with property path like `user.projects` 2. parent level `join` table **MUST** be set before children like `join=users&join=users.projects&join=users.projects.tasks`
|
Hi @Diluka, thanks for your effort. Could you please add changes to the |
Diluka
commented
Jan 23, 2019
|
@zMotivat0r All checks have passed lol |
michaelyali
approved these changes
Jan 25, 2019
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
new feature to support nested relation query
joincan be set with property path likeuser.projectsjointable MUST be set before children likejoin=users&join=users.projects&join=users.projects.tasksoptionsshall be placed into eachjoinconfig although it's the sameEntityconfigured by others due to theoptionsdesign. Suggest the future version to move@Cruddecorator fromcontrollerstoentities. And with the concept in auto generate everything from entity #26, the overall configuration will be greatly simplified.close #23 this feature resolve this issue