Skip to content

Make testInboxID optional param #70

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 5 commits into from
Jul 2, 2025
Merged

Conversation

narekhovhannisyan
Copy link
Collaborator

@narekhovhannisyan narekhovhannisyan commented Jul 1, 2025

Motivation

Unblock using the testing api without testInboxId.

Summary by CodeRabbit

  • Bug Fixes

    • Improved error handling when sending mail in sandbox mode, ensuring clearer messages if required information is missing.
  • Documentation

    • Added documentation for the templates feature.

Copy link

coderabbitai bot commented Jul 1, 2025

Walkthrough

The changes introduce a private validation method in MailtrapClient to ensure testInboxId is present in sandbox mode, updating send, batchSend, and the testing getter to use this method. URL construction now conditionally appends testInboxId only when sandbox mode is active and the ID is provided. Corresponding tests were added and redundant ones removed.

Changes

File Change Summary
src/lib/MailtrapClient.ts Added private validateTestInboxIdPresence() method; reordered error constants; refactored testing getter; updated send and batchSend to validate testInboxId and conditionally append it to URLs; added JSDoc for templates getter.
src/tests/lib/mailtrap-client.test.ts Added tests verifying send() and batchSend() throw error if testInboxId missing in sandbox mode; replaced redundant testing getter test; reordered error constants; added test for testing getter returning TestingAPI when accountId present without testInboxId.

Possibly related PRs

  • Restructure SDK #51: The main PR and this one both modify MailtrapClient error handling and sandbox mode validation, showing a direct connection in client send logic and error management.
  • Batch Sending Api #63: Introduced the batchSend method and related tests; this PR builds on that by adding sandbox validation for batchSend and send.

Suggested reviewers

  • VladimirTaytor
  • mklocek

Poem

A hop and a skip through the code we go,
With errors in order, and checks in tow.
Now sandbox is safe, test inbox in sight,
URLs are tidy, everything’s right!
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d7f7042 and 1e10d77.

📒 Files selected for processing (1)
  • src/__tests__/lib/mailtrap-client.test.ts (4 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • src/tests/lib/mailtrap-client.test.ts
✨ Finishing Touches
  • 📝 Generate Docstrings

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.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6d5ba68 and 0a2d134.

📒 Files selected for processing (1)
  • src/lib/MailtrapClient.ts (3 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
src/lib/MailtrapClient.ts (1)
src/lib/MailtrapError.ts (1)
  • MailtrapError (1-1)
🔇 Additional comments (4)
src/lib/MailtrapClient.ts (4)

35-35: LGTM: Minor reordering of constants.

The reordering of error constants doesn't affect functionality but appears to be a stylistic preference.


131-133: LGTM: Improved documentation.

Good addition of JSDoc comment for consistency with other getter methods.


167-169: LGTM: Appropriate validation for sandbox mode.

The validation correctly enforces that testInboxId is required when in sandbox mode, aligning with the PR objective of making it optional for other use cases.


172-172: LGTM: Correct URL construction logic.

The updated URL construction appropriately includes testInboxId only when both sandbox mode is active and testInboxId is present.

@@ -664,20 +706,6 @@ describe("lib/mailtrap-client: ", () => {
});

describe("get testing(): ", () => {
it("rejects with Mailtrap error, when `testInboxId` is missing.", () => {
Copy link
Contributor

Choose a reason for hiding this comment

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

It would also be nice to have a test that the absence of testInboxId doesn't raise an error when client.testing is called.

Copy link
Contributor

Choose a reason for hiding this comment

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

And remove testInboxId from all client setup cases where it's not needed anymore (like here).

@narekhovhannisyan narekhovhannisyan merged commit c5f1d30 into main Jul 2, 2025
4 checks passed
@narekhovhannisyan narekhovhannisyan deleted the optional-test-inbox branch July 2, 2025 14:17
@vittorius vittorius mentioned this pull request Jul 8, 2025
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