Sendgrid Plugins

[amolkokane-cirus]

Fixed an issue with macros not working
Added missing javadocs
Changed copyright to 2020

[rmstar]

Input schema can be null if the previous stage's output schema is a macro.

[rmstar]

Please try testing with a pipeline where schema fields are macro params. You could try something like source -> wrangler -> sendgrid sink

[amolkokane-cirus]

TODO

[rmstar]

TODO should be in the code, not a comment on the PR.

[shiva-cirus]

Code updated with ToDO and created JIRA issue https://issues.cask.co/browse/PLUGIN-359

[rmstar]

Please write a more descriptive comment.
Also, @return string doesn't tell us what is being returned. We already know that the return type is String.
Similar comment in other places in the PR.

[amolkokane-cirus]

Done

[rmstar]

why is this the opposite of checkFrom?
if (!Strings.isNullOrEmpty(config.getReplyTo()) && validateEmail(config.getReplyTo()))
vs
if (Strings.isNullOrEmpty(config.getFrom()) || !validateEmail(config.getFrom()))

[amolkokane-cirus]

This is opposite because ReplyTo config is not mandatory. Moreover, we found another bug in the same validation code so fixed that too.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.