Your markdown is horrible. Most things don's parse, and you can't even preview stuff.
Your markdown is horrible. Most things don's parse, and you can't even preview stuff. Add a preview tab.
Owen Scott commented
Microsoft, what is happening here?!? You've had a completely broken product in the field for months, and there are like a half-dozen user voice posts about it. This isn't a request for improvement - you've literally shipped something that doesn't work.
Try typing the following and tell me that I'm wrong:
> The first variable is named `var1` and the second variable is named `var2`
In examples like this you get an inline code span for "var1" (most of the time) but never for "var2". Please fix! I don't want to see any new features added to Teams before this basic issue is solved...
Morgan Jones commented
To add to this point, it's also extremely frustrating that you use a different flavour of markdown to all of the other markdown based applications available. All (almost) other applications use github flavour markdown, why would you not use this?
Jamie Thomson commented
Your markdown support really is bad, not only that it's gotten worse in the most recent release because the single backtick no longer has the desired effect - it arbitrarily converts the text to italics.
I'll say what I've said in countless other feedback submissions (and in twitter messages to Teams engineering members), just let us write raw markdown, don't convert it on the fly, then let us preview the rendered markdown prior to posting. Simple.