Notification frameworks #162
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
Closed
renetapopova
force-pushed
the
diagnostic-info
branch
from
51f863a to
65de763
Compare
Lojjs
requested changes
Aug 16, 2024
Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
Lojjs
reviewed
Aug 20, 2024
Lojjs
reviewed
Aug 20, 2024
| The GqlStatusObject API provides information about the status of a Cypher query or command execution in compliance with the GQL standard. | ||
|
|
||
| The notification object, which is part of the result summary, consists of the following fields: | ||
| This page describes both the Neo4j Notification and the GQL-status object frameworks, how they are structured, the objects they provide for notifications, and how to interpret them. |
There was a problem hiding this comment.
I think we are still not fully consistent on naming. Should we stick to GqlStatusObject (this is what it is called in the codebase) when we talk about the framework/API and GQL-status object (this is what it is called in GQL standard) if we talk about the actual object a user get back or what do you think? Can you read through and check that it is consistent?
Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
Lojjs
reviewed
Aug 20, 2024
Co-authored-by: Louise Berglund <louise.berglund@neo4j.com>
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
Lojjs
approved these changes
Aug 20, 2024
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.