forked from introproventures/graphql-jpa-query
-
Notifications
You must be signed in to change notification settings - Fork 0
update master #6
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
Merged
Merged
Conversation
This file contains hidden or 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
* add DroidFunction to StarWars model for example and test, use as primaryFunction in Droid * update SQL for example and tests to create DroidFunction records and reference them in Droid records * update test queryForDroidByName to expect DroidFunction to be nested * add tests for where clauses on many-to-one relationships, the nested one currently failing * that was not the droid I was looking for * move DroidFunction into starwars package * restore DroidFunction into starwars package * update example sql data to include droid_function entity * account for droid_function in newly merged tests * feat: implemented many to one relation criteria expression * chore: clean up code * feat: add nested one-to-many criteria expression support * fix: use default distinct configuration in one-to-many data fetcher * fix: polish test formatting
* feat: extract JPA entities into separate modules * fix: update model pom versions * chore: rename example modules and models * fix: add graphql-jpa-query-example-simple in Dockerfile * fix: merge conflicts
* fix MappedSuperclass support * fix: set logging.level.org.hibernate=info
* fix: compound nested relationship criteria expressions * fix: remove test comments * fix: disable failing Travis JDK 11 build
) * fix: Apply left outer join to retrieve optional associations * chore: polish GraphQLJPASchemaBuilder * chore: clean DriodFunction orphan * fix: change primaryFunction association type to @OnetoOne * feat: first crack at optional argument join handling * fix: set author association type to optional=false * fix: add optional unit tests * fix: compile error
… Java classes (#130) * feat: provide fallback Object default for JavaScalars * feat: create alias for Object Scalar type by default
* feat: add equals criteria support for custom attributes converters * fix: failing tests * fix: clean up code and improve tests * fix: polish tests
* feat: add IN | NIN predicate for custom attribute types * fix: add more tests
* feat: add criteria list schema support * feat: implement criteria list query support * feat: add criteria list unit tests
* feat: add optional argument parameter for plural attributes * feat: add optional one-to-many tests * fix: polish tests queries * fix: polish optionalArgument method * fix: make collections join fetch default optional true * feat: add join fetch collection auto configuration property * fix: RTE with explicit optional and nested orderBy * fix: add more tests
* fix: correct element collection fetch sort order * fix: remove @ignore from queryOrderByFieldsNested
…ns (#151) * feat: test exists criteria api * feat: add correlation subquery testers * feat: add singular EXISTS logical subquery expression * feat: add list EXISTS criteria expressions * feat: add NOT_EXISTS subquery criteria expression * feat: add SubqueryCriteriaExpression GraphQLInputObjectType * fix: add array EXISTS subquery support * feat: add custom attribute EXISTS subquery test * fix: disable show sql because of long log Travis failure * fix: implement missing equals() and hashCode() methods * fix: add implicit EXISTS subquery test for custom attributes * fix: enable openjdk11 in .travis.yaml
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.
No description provided.