New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add help + Wiki page #15
Comments
I don't mind working on this. Just a few questions.
I work on these things in my off time, so it might take me a few weeks (definitely before the end of #hacktoberfest |
Hi @tigerfansga
I think we could agree, and say we want only to generate the help files from functions that are located in the Public folder (https://github.com/Stephanevg/PSClassUtils/tree/master/Functions/Public ) In powershell, this would probably be: Get-childItem -Path $PsScriptRoot\Functions\Public
|
Thanks @Stephanevg I will get to working on it. One thing on answer #1, so if you look at the README.md for PlatyPS it gives two "Common setups" 1. Using markdown as the source of truth and generate compiled help - this is what I was thinking of when I asked about removing the comment based help, help would still be available for the user - or 2. Keeping comment based help and generating markdown. Based on your answer, I will go with path 2 unless you decide otherwise. I don't mind working on issue #16 after the help part is done. I definitely don't mind look at some automation. Maybe moving to something like psake for your build process. It would simplify the yaml |
Cool! |
I will do. I updated my last comment because I had missed the automation piece. Take a look for future ideas on automation. |
Hi @Stephanevg Wanted to give you a quick status. First, my normal development environment is using a Ubuntu machine with PSCore 6.1. I have forked the project and created a branch issue-15. I have done a quick first pass using platyPS. Just a few items of note.
It may take me a few days, but I will setup a Windows environment to make sure there are no platform issues. |
Hi @tigerfansga To address your topics:
Here are my remarks, directly on a screen shot. Each topic is anotated with 'a', 'b' etc.. so we can discuss easily about these topics. Also, the Notes sections isn't that nicely formatted. Any idea how we could make it prettier? A lost thing, I saw you have help for the function |
Hi @Stephanevg
On your remarks I will look at the Notes to see what needs to be done. On the Private functions, again I just did a quick pass, once automated these will be gone. |
ok, awesome! 👍 |
So on item b above, it is related to the way markdown is interpreting the -‘s used to format the comment based help. I will have to play with it some more to see how to fix it |
hi @tigerfansga have you any news on this one? |
Sorry, I’ve not had much chance to look. This weekend I should. |
Evening @Stephanevg I spent a little time today playing with this. Main item learned, the output from PlatyPS is different on Linux than Windows. One must always keep in mind PSCore, especially on Linux or MacOS is not the same as Windows PowerShell. The markdown generated is much closer to the comment based help when run from Windows PowerShell. There are still a few things that don't convert exactly right. The big item is the formatting of the examples. Markdown doesn't treat spaces the same as comment based help does. I will start to research how we can make things line up properly. We will probably have to modify the current comment based help to have it match up. My current plan is to get the comment based help to generate the markdown to match and update the CI to run the commands to generate the markdown. I have pushed the output of |
Could I ask for some use case examples when you mentioned " comment based help to generate the markdown" |
All commandlets have Comment based help + examples
It would be great to have help extracted into individual markdown pages (using PlatyPS for example).
The text was updated successfully, but these errors were encountered: