Skip to content

Conversation

CommanderStorm
Copy link

@CommanderStorm CommanderStorm commented Jun 11, 2025

There are quite a few rust modules missing.
These are just the modules for which there already exists a file.

CC @DDtKey

@CommanderStorm CommanderStorm requested a review from a team June 11, 2025 17:01

let postgres_instance = postgres::Postgres::default().start().unwrap();

let connection_string = format!(
Copy link
Member

Choose a reason for hiding this comment

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

suggestion: here in the catalog, we usually just add the container instance declaration, avoiding the addition of more in depth info on how to connect to them. We delegate that to the final docs for each language

Copy link
Author

Choose a reason for hiding this comment

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

fair enough. I just copied the examples from docs.rs ^^

Not quite sure what this means concretely for the modules as noted below 😅

maintainer: community
example: |
```rust
use testcontainers_modules::{testcontainers::runners::SyncRunner, mssql_server};
Copy link
Author

Choose a reason for hiding this comment

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

this one needs accepting the eula.. lets keep it ^^

url: https://docs.rs/testcontainers-modules/latest/testcontainers_modules/oracle/free/struct.Oracle.html
maintainer: community
example: |
```rust
Copy link
Author

Choose a reason for hiding this comment

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

lets keep the warning ^^

maintainer: community
example: |
```rust
use testcontainers::core::ImageExt;
Copy link
Author

Choose a reason for hiding this comment

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

since this does not work otherwise, here I am keeping the imports.
It is otherwise a bit confusing

Copy link
Contributor

Choose a reason for hiding this comment

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

It's technically possible to call this like <.. as testcontainers::core::ImageExt>

But I definitely agree that import is way better for trait here

@CommanderStorm
Copy link
Author

@mdelapenya is there any feedback for me to integrate?
Should I break this PR apart instead to make it more reviewable?

maintainer: community
example: |
```rust
use testcontainers::core::ImageExt;
Copy link
Contributor

Choose a reason for hiding this comment

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

It's technically possible to call this like <.. as testcontainers::core::ImageExt>

But I definitely agree that import is way better for trait here

CommanderStorm and others added 2 commits August 17, 2025 23:29
Co-authored-by: Artem Medvedev <[email protected]>
Co-authored-by: Artem Medvedev <[email protected]>
@CommanderStorm CommanderStorm requested a review from DDtKey August 17, 2025 21:30
@mdelapenya
Copy link
Member

@CommanderStorm I'll delegate the final review to @DDtKey, as core maintainer of tc-rust, not being myself a rust developer. Once approved, I can merge this PR

In any case, your humungous work in updating all the modules is amazing, thank you so much for this. The TC catalog will look amazing for the Rust community! 🚀

@CommanderStorm
Copy link
Author

Well.. this is only like 50% of the modules avaliable.
There are 47 rust Testcontainers in total, the rest is not in the catalogue already so splitting prs on this front

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.

3 participants