You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Locally, I edited an .md file, doing the kind of writing we would do for a cmdlet. This is part of creating our round tripping procedures.
When I added bold or italics and then round tripped, the markup was gone, but so was the space before and after the marked word. (Using screen caps here so as not to confuse the markdown in this issue editor:)
Although it would be nice to have a way to maintain formatting through the round trip process, even if we don't do that, some contributors will use formatting anyway (since it is allowed and expected in markdown) so we can't have spaces disappearing.
The text was updated successfully, but these errors were encountered:
What exactly do you mean by round trip?
If you are talking about Markdown -> Maml -> Markdown, then it's expected, and nothing we can do about it. Maml schema doesn't allow us store all the things we want to store (i.e. parameter set names).
But that's not the suggested workflow.
Suggested workflow is: keep source of truth in Markdown. Use Update-MarkdownHelp to update it. Generate MAML as a build step and don't store it anywhere.
Locally, I edited an .md file, doing the kind of writing we would do for a cmdlet. This is part of creating our round tripping procedures.
When I added bold or italics and then round tripped, the markup was gone, but so was the space before and after the marked word. (Using screen caps here so as not to confuse the markdown in this issue editor:)
Although it would be nice to have a way to maintain formatting through the round trip process, even if we don't do that, some contributors will use formatting anyway (since it is allowed and expected in markdown) so we can't have spaces disappearing.
The text was updated successfully, but these errors were encountered: