Skip to content
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

xWaitForADDomain: This resource is missing comment-based help #341

Closed
johlju opened this issue Jun 7, 2019 · 6 comments · Fixed by #435
Closed

xWaitForADDomain: This resource is missing comment-based help #341

johlju opened this issue Jun 7, 2019 · 6 comments · Fixed by #435
Labels
enhancement The issue is an enhancement request. good first issue The issue should be easier to fix and can be taken up by a beginner to learn to contribute on GitHub

Comments

@johlju
Copy link
Member

johlju commented Jun 7, 2019

This resource is missing comment-based help for the functions.

@johlju johlju added enhancement The issue is an enhancement request. good first issue The issue should be easier to fix and can be taken up by a beginner to learn to contribute on GitHub help wanted The issue is up for grabs for anyone in the community. labels Jun 7, 2019
@johlju johlju added this to To do in All issues and PR's Jun 7, 2019
@X-Guardian
Copy link
Contributor

@johlju How can this help be displayed?

@johlju
Copy link
Member Author

johlju commented Jun 12, 2019

We have "debated" this in general in the issue PowerShell/DscResources#253 if we need this or not. The conclusion was that this is not for the users but for the contributors to add notes about design choices. The style guideline also has this entry https://github.com/PowerShell/DscResources/blob/master/StyleGuidelines.md#functions-have-comment-based-help
In reality it is mostly not used in that way unfortunately (with the exception of PSDscResources) so mostly it just the synopsis and the parameters with the same text as in the schema.mof. Helper functions is not documented else where, so that is good that those parameters are documented in the comment-based help.
But the whole comment-based help be or not be could be discussed again since there are new contributors and maintainers since the last time.

Though, I will not enforce that there need to be an .EXAMPLE (saw it in the style guideline just now) . An issue should really be opened to removed that from the style guideline, no maintainer enforces that what I have seen.

@X-Guardian
Copy link
Contributor

OK, no use to end users then. I've been experimenting with the about*.help.txt files that the New-DscResourcePowerShellHelp generates, and these are much more useful for the end user, as they are dynamically built from the MOF data and example files and allow you to run get-help on the resource name to show them. There is currently no mention of these in the style guidelines.
Currently the New-DscResourcePowerShellHelp function outputs these files all to one directory, but could be easily changed to output them to the en-US folder of each DSCResource, which for me seems a more logical location. Get-Help will find the files there.
I think we should update this function and populate the module with these files. What do you think?

@johlju
Copy link
Member Author

johlju commented Jun 25, 2019

I like the idea of adding the `about*.help.txt files to help the ends users. We should also update the GitHub pull request template that these should be updated (so that I remember to enforce it), and also it would be good to open an issue in the DscResource repo for this to be added to the style guideline.

This would not replace the comment-based help though, that I think is still needed for the developers for design choices etc.

@X-Guardian
Copy link
Contributor

Yes, agreed. different audience.

I raised this PR PowerShell/DscResource.Tests#325 to make the New-DscResourcePowerShellHelp function more useful for this. We could then take it further and add a meta-test that checks that the help files are there and are correct...

If you want to raise an issue for the about_help files in this repo, I'll populate all of them from the output of the function.

@RobertCGouge
Copy link
Contributor

I am going to take a shot at this.

All issues and PR's automation moved this from To do to Done Jul 15, 2019
Remove 'x' from module name automation moved this from To do to Done Jul 15, 2019
johlju pushed a commit that referenced this issue Jul 15, 2019
Changes to xWaitForADDomain
- Added comment-based help (issue #341).
@johlju johlju removed the help wanted The issue is up for grabs for anyone in the community. label Jul 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement The issue is an enhancement request. good first issue The issue should be easier to fix and can be taken up by a beginner to learn to contribute on GitHub
Projects
Development

Successfully merging a pull request may close this issue.

3 participants