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 email scheduling #33

Merged
merged 3 commits into from
Aug 15, 2024
Merged

feat: Add email scheduling #33

merged 3 commits into from
Aug 15, 2024

Conversation

kewynakshlley
Copy link
Collaborator

  • Create email with schedule
  • Update email schedule
  • Cancel schedule
  • Removed date types

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature.
* @param scheduledAt The schedule of the email in ISO 8601 format (e.g., 2024-08-05T11:52:01.858Z).
* @return This builder instance for method chaining.
*/
public Builder scheduledAt(String scheduledAt) {

Choose a reason for hiding this comment

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

Should we instead use withScheduledAt in the Builder? If this is how it's done in the others Builders, I vote to keep consistent, but if this is the first, I think that using the with prefix makes more sense with the Builder way

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I don't use the 'with' prefix in the other builders. I would prefer to keep it this way without the 'with' prefix to keep the code consistent.

@kewynakshlley kewynakshlley merged commit 981a0ad into main Aug 15, 2024
1 check passed
@kewynakshlley kewynakshlley deleted the feat/schedule branch August 15, 2024 18:29
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.

None yet

2 participants