-
Notifications
You must be signed in to change notification settings - Fork 16
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
Research: Newline rendering in Teams messages via Office 365 Connector Cards #58
Comments
Or it can remain, and be adapted to handle replacing a literal single use of |
Now that recent work has been done to move the formatting functions of this project ( |
While researching whether Markdown tables are supported via webhook requests (spoiler: it does not appear so), I stumbled across this line:
This is particularly useful to know, as I ended up going this route to work around the discovered behavior:
https://github.com/atc0005/send2teams/blob/170ac3bc6932c575174dd9ab1ccf84b39a001776/teams/teams.go#L31-L49
https://github.com/atc0005/send2teams/blob/170ac3bc6932c575174dd9ab1ccf84b39a001776/teams/teams.go#L255-L271
I don't recall off the top of my head where I learned that
<br>
was a good replacement, but it served the use case. Now it sounds like theConvertEOLToBreak()
function can be deprecated and one put in its place to substitute\n\n
instead.The text was updated successfully, but these errors were encountered: