Skip to content

Fix browser tests in the lite driver #5

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
May 25, 2023

Conversation

bigmontz
Copy link

The basic browser tests in the lite driver is done by using a WebSocket implementation in a mocked browser. So, mocking the window is needed.

bigmontz added 2 commits May 24, 2023 16:44
The basic browser tests in the lite driver is done by using a WebSocket implementation in a mocked browser.
So, mocking the `window` is needed.
`boltAgent` is not configurable, so it should not be exposed in the `Config`.
The `InternalConfig` interface was created for keeping the type-safety.

The declaration tests were failing because of multiple `AbortSignal` definitons.
This was happening because each project is using different versions of `@types/node` in the `package-lock.json`.
The problem was not happening before because any interface exposed by the `neo4j-driver-core` was depending in Node defintions.
The solution can be done or by remove the Node api  reference or by pin the  `@types/node` versions accross all packages.
The first solution was choosed since the use of `string` instead `NodeJS.Platform` in the `SystemInfo` doesn't impact the usability of the `node.boltAgent.fromVersion` function.
@ConorNeo ConorNeo merged commit 2c97a5d into ConorNeo:bolt-agent May 25, 2023
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