New-MarkdownHelp - Fix #720#724
Closed
Jaykul wants to merge 1 commit intopester:masterfrom
Closed
Conversation
Contributor
|
Generally I agree with your idea to move help but
|
Contributor
Author
|
Yeah, like my fixes for gherkin in #715 ;-) |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Create a branch for PlatyPS help to address #720
Initially, just import
New-MarkdownHelp -Module Pester -OutputFolder Docs -WithModulePageI recommend we not merge to DevelopmentV4, but create a branch. Before merging, we should get a
Buildto run PlatyPS on the source markdown to build the xml help, and then retrofit all the functions to reference the xml files instead of having comments...