Craig E. Shea

I suppose the resolution here could be one of two things: 1. Update platyPS to "just work" (i.e. work as expected)—skip the generation of markdown help when it already exists...

Where platyPS comes into play is that it does not accept trailing spaces nor a backslash after any related link markdown. platyPS emits an error when generating the MAML.

Well, I'm happy to report that other than this issue I ran into, so far, I've been able to generate the PS help documentation for my module. Thanks for the...

One workaround for this issue is to separate the lines with an additional newline in between. This forces each link into its own separate paragraph and renders correctly in BitBucket...

Hmm, I was going to suggest just inheriting from `HelpText`, but it seems there are no virtual members to override! Perhaps there should be an interface or abstract base class...

@guludo Your response is spot on. I created a React app using `yarn create react-app my-app --template typescript`, followed the directions to migrate from yarn 1.22.x to 2.x and received...

Oh, and one more comment on this, I did _not_ need to use `nodeLinker: node_modules` in the `.yarnrc.yml` file, as was stated on the migration page, typescript works just fine...

This is still happening as of SQL Server 2017 CU14 and 2019 CTP 2.5 using Docker Desktop and LCOW. Docker Desktop: 2.0.4.0 (33772), Edge Engine: 19.03.0-beta3 Compose: 1.24.0 Windows 10...

This is really a function of the CSS stylesheet used to style the HTML when converting Markdown to HTML.

I agree with @melkster, a plugin should not override default vim commands. And if a plugin author _really_ wants to use a keymap that conflicts with a default vim command,...