docs: Explain immutable builder behavior#1693
Conversation
✅ Deploy Preview for testcontainers-dotnet ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughThis PR makes two independent updates: bumping MongoDB.Driver to 3.8.1 and adding documentation explaining Testcontainers builder immutability with practical reuse examples. ChangesMaintenance and Documentation Updates
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Warning Review ran into problems🔥 ProblemsGit: Failed to clone repository. Please run the Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What does this PR do?
Occasionally, developers run into misunderstandings about how the fluent builder API in Testcontainers works. Testcontainers builders are immutable. Every builder method returns a new instance that includes the updated configuration, while the existing builder instance remains unchanged.
Why is it important?
To make this behavior clearer and more explicit for developers, this PR documents it.
Related issues
Summary by CodeRabbit
Chores
Documentation