Skip to content

Update karma dependencies on neo4j-driver #1131

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 2 commits into from
Aug 18, 2023

Conversation

bigmontz
Copy link
Contributor

This PR also fix some tests which are using done/async in a inconsistent way.

This solves: https://github.com/neo4j/neo4j-javascript-driver/security/dependabot/107

This PR also fix some tests which are using done/async in a inconsistent way.

This solves: https://github.com/neo4j/neo4j-javascript-driver/security/dependabot/107
Comment on lines +276 to +277
it('should reset and flush when SUCCESS received', done => {
createConnection(`bolt://${sharedNeo4j.hostnameWithBoltPort}`).then(conn => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this one not async and using await?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

there is no await here. The async/await was removed from this test since we need to work with promises to be able to call resetAndFlush and simulate some protocol messages before the resolution of the promise. There are other tests doing something similar.

The mix of async/await with the callback done is not supported anymore in newer versions of karma, the is actually good.

@bigmontz bigmontz merged commit 1e11be2 into neo4j:5.0 Aug 18, 2023
@bigmontz bigmontz deleted the 5.x-update-karma-dependencies branch August 18, 2023 12:17
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.

2 participants