Skip to content
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

feat: add Neo4j module #937

Merged
merged 3 commits into from
Mar 27, 2023
Merged

feat: add Neo4j module #937

merged 3 commits into from
Mar 27, 2023

Conversation

fbiville
Copy link
Contributor

@fbiville fbiville commented Mar 10, 2023

What does this PR do?

This introduces support for Neo4j containers.

Why is it important?

Neo4j is great database (I'm not biased at all /s) and deserves proper TestContainers support in Go.

Related issues

@netlify
Copy link

netlify bot commented Mar 10, 2023

Deploy Preview for testcontainers-go ready!

Name Link
🔨 Latest commit 9af0296
🔍 Latest deploy log https://app.netlify.com/sites/testcontainers-go/deploys/6421651fff2cf1000740e6ac
😎 Deploy Preview https://deploy-preview-937--testcontainers-go.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

Copy link
Member

@mdelapenya mdelapenya left a comment

Choose a reason for hiding this comment

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

Wow, great PR @fbiville! Thank you very much for your time. I'm only missing docs on the public API

What do you think if we add docs in the same way that we do for localstack or pulsar? I'd start using any of them as example, describing the different options:

Once there, I think this is ready to go! 🚀

modules/neo4j/neo4j.go Outdated Show resolved Hide resolved
@fbiville
Copy link
Contributor Author

I started with a minimal documentation page.
There is also a list of other features to support listed in the initial comment of this PR.

Shall I complete the docs for the current feature set and work on the other features in subsequent PRs?
(I'll be on vacation next week, but I can resume the work when I'm back)

@mdelapenya
Copy link
Member

Shall I complete the docs for the current feature set and work on the other features in subsequent PRs?

As the neo4j module won't appear until the next release, I think it's fine to set this as ready-for-review and eventually merge this PR, and continue with the extensions in follow-up PRs.

Thanks for contributing this module! Looks promising!

@mdelapenya
Copy link
Member

I did not mention, but we are writing down a design doc for modules so, once approved, we will eventually update all existing modules to that design.

This wants to reinforce the message of "progress, simple perfection" that I learnt at my time at Elastic :) So go for it adding incremental changes in small batches

@mdelapenya mdelapenya self-assigned this Mar 21, 2023
@mdelapenya mdelapenya added the enhancement New feature or request label Mar 21, 2023
@fbiville fbiville marked this pull request as ready for review March 24, 2023 14:56
@fbiville fbiville requested a review from a team as a code owner March 24, 2023 14:56
mdelapenya
mdelapenya previously approved these changes Mar 27, 2023
Copy link
Member

@mdelapenya mdelapenya left a comment

Choose a reason for hiding this comment

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

LGTM! Thanks for the module for such a great technology!

As I said, we are planning to standardise how to create options, so we probably update the code in a follow-up PR with some design changes, but we prefer seeing progress here merging the PR and iterating in small chunks later. Will ping you in there.

Thanks again for your work in this PR

@fbiville
Copy link
Contributor Author

@mdelapenya now rebased

@sonarqubecloud
Copy link

sonarqubecloud bot commented Mar 27, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
No Duplication information No Duplication information

@mdelapenya mdelapenya merged commit 8da81cf into testcontainers:main Mar 27, 2023
@mdelapenya mdelapenya changed the title Neo4j feat: add Neo4j module Mar 27, 2023
@fbiville fbiville deleted the neo4j branch March 27, 2023 13:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Implement neo4j as a Go module
2 participants