-
Notifications
You must be signed in to change notification settings - Fork 52
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
Request: Add TargetLinkUrl to MessageEvent #152
Comments
Create a Pull Request so this can be implemented |
@Richard-West Funny you should mention this today as I was just thinking this morning I'd just go ahead and do it. Is this something you're after as well or were you just giving me a little push? ;) |
Pull request submitted. |
We were looking for this same functionality earlier today!
Richard West
…________________________________
From: zythra <[email protected]>
Sent: Wednesday, October 11, 2017 5:54:46 PM
To: darrencauthon/csharp-sparkpost
Cc: Richard West; Mention
Subject: Re: [darrencauthon/csharp-sparkpost] Request: Add TargetLinkUrl to MessageEvent (#152)
@Richard-West<https://github.com/richard-west> Funny you should mention this today as I was just thinking this morning I'd just go ahead and do it. Is this something you're after as well or were you just giving me a little push? ;)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#152 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AD_YW9XIICThbBDAGsPICXgaKuUHMVrgks5srTkmgaJpZM4PhFDN>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Can TargetLinkUrl be added to MessageEvent please? I've added it in a cloned repo, but the change is so small I don't know that it's worth creating a pull request for it. It was as simple as adding the property to MessageEvent and adding the mapping "TargetLinkUrl = result.target_link_url" in the ConvertResultsToAListOfMessageEvents() method in the MessageEvents class.
Thanks!
The text was updated successfully, but these errors were encountered: