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

GH-643 - Make sure all kinds of enums are correctly identified. #644

Merged
merged 1 commit into from
Jul 3, 2019

Conversation

michael-simons
Copy link
Collaborator

This fixes #643.

@michael-simons michael-simons merged commit bab8271 into 3.1.x Jul 3, 2019
@michael-simons michael-simons deleted the issue/gh643 branch July 3, 2019 09:57
michael-simons added a commit that referenced this pull request Apr 6, 2020
This removes the new API on the AnnotationInfo. This API was very well done and tested, but it increases our surface again and we don’t want that. It’s needed in two places and it’s ok to duplicate it the instantiation there.

There’s one signifacant change we’re we check whether the attribute is an enum or not.  For comparision: #644
michael-simons added a commit that referenced this pull request Apr 7, 2020
… enum.

This adds `org.neo4j.ogm.annotation.Relationship.Direction` to the `@Relationship` annotation which replaces the String-typed property `direction` on that annotation.

The `AnnotationInfo` needs to check now whether it targets an enum or not. We use the same mechanism introduced as in #644.

The changes allows for some neat and needed refactoring, especially in the `EntityGraphMapper` and in `ClassInfo`.

Co-authored-by: Michael Simons <michael.simons@neo4j.com>
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

Successfully merging this pull request may close these issues.

1 participant