Entity and connections API#308
Merged
Merged
Conversation
angrykoala
approved these changes
Apr 27, 2026
| == Distinction | ||
|
|
||
| The API split is mainly due to development-historic reasons. | ||
| The entity API came first and is simpler and more performant, while the connections API allows for relationship traversal, accessing relationship fields, aggregations and more. |
Member
There was a problem hiding this comment.
While this is partially true, I don't think it is too relevant for users the historic reasons.
Just stating the main differenceces should be enough: Entity API allows for simple traversal, whilst connectons API allow access to relationship proerties, more complex features (such aggregations) and it is Relay compatible
…-graphql into entity-api-vs-connections-api
lidiazuin
reviewed
Apr 28, 2026
|
|
||
| == Links | ||
|
|
||
| * xref:directives/schema-configuration/index.adoc[] - Configure your schema and limit field accessibility |
Contributor
There was a problem hiding this comment.
I think all these topics should have a full stop, maybe? And follow the same style
Contributor
Author
There was a problem hiding this comment.
added suggestions
rsill-neo4j
commented
Apr 28, 2026
rsill-neo4j
commented
Apr 28, 2026
rsill-neo4j
commented
Apr 28, 2026
Co-authored-by: Lidia Zuin <102308961+lidiazuin@users.noreply.github.com> Co-authored-by: Richard Sill <156673635+rsill-neo4j@users.noreply.github.com>
rsill-neo4j
commented
Apr 28, 2026
Collaborator
|
This PR includes documentation updates New pages: Updated pages: |
lidiazuin
reviewed
Apr 28, 2026
Co-authored-by: Lidia Zuin <102308961+lidiazuin@users.noreply.github.com>
lidiazuin
approved these changes
Apr 28, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.