Disclaimer note about Java driver and reference #158
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
✅ Deploy Preview for neo4-docs-java-reference ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
renetapopova
approved these changes
Nov 13, 2023
Collaborator
renetapopova
left a comment
renetapopova
left a comment
There was a problem hiding this comment.
Looks good to me. Thanks, @lidiazuin!
lidiazuin
added a commit
to lidiazuin/docs-java-reference
that referenced
this pull request
Nov 13, 2023
lidiazuin
added a commit
to lidiazuin/docs-java-reference
that referenced
this pull request
Nov 13, 2023
lidiazuin
added a commit
that referenced
this pull request
Nov 13, 2023
lidiazuin
added a commit
that referenced
this pull request
Nov 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
A customer who wanted to create a transaction event listener was confused by what classes they needed to import and use to make it work. Clarification that this section in the docs is specific to server-side code and deployment could avoid future occurrences like this.