Conversation
|
|
||
| $docsPath = Join-Path $data.ProjectRoot -ChildPath 'docs' | ||
|
|
||
| if (Test-Path -Path $docsPath) { |
There was a problem hiding this comment.
why would we removing existing docs, md files in docs shoudl be considred as source of truth. They are modified manually and should not be removed/regenerated on every build.
There was a problem hiding this comment.
I had to take a slightly different approach, focus is to generate the final MAML files from Markdown docs. Your pull request is focusing on generating the markdown files.
Core functionality of ModuleTools is to generate module that can be published directly to PSGallery or private repos. How user generates and stores mardkown in platyps format under docs folder is completely up to user and should be flexible. We will only bundle and ship the said md files as MAML help in module.
|
Similar logic has been adopted into the main branch. Closing this Pull request. |
2 participants
Closes Issue #18