-
-
Notifications
You must be signed in to change notification settings - Fork 9
Feature Request: Expand Comment-Based Help Content of ResourceType and PropertyType Functions #61
Comments
This is great!!! Definitely going to expand it a bit, totally makes sense and adds a ton of value!! Thank you for the suggestion and sample code! |
Awesome. Also, when running my code example, all of the WARNING messages that will pop-up are directly related to problems having to do with both the AWS CFN UserGuide documentation and the
|
Incredibly valuable, thank you so much for sharing!! Also, contributors are very much welcome if interested! It seems like we've been solving a lot of the same things from different aspects. I appreciate your insight and suggestions @ScriptAutomate! |
## 2.9.0 - 2019-09-08 * [Issue #61](#61) -- _Thanks, [@ScriptAutomate](https://github.com/ScriptAutomate)!_ * Updated Parameter help for all Resource Type and Property Type functions to include the Parameter descriptions. * [Issue #62](#62) -- _Thanks, [@ScriptAutomate](https://github.com/ScriptAutomate)!_ * Updated the CI build process to check all spec sheets for any Resource Types and Property Types that may be missing from `us-east-1`. * Miscellaneous * Brought Resource Type and Property Type functions up to current spec sheet.
## 2.9.0 - 2019-09-08 * [Issue #61](#61) -- _Thanks, [@ScriptAutomate](https://github.com/ScriptAutomate)!_ * Updated Parameter help for all Resource Type and Property Type functions to include the Parameter descriptions. * [Issue #62](#62) -- _Thanks, [@ScriptAutomate](https://github.com/ScriptAutomate)!_ * Updated the CI build process to check all spec sheets for any Resource Types and Property Types that may be missing from `us-east-1`. * Miscellaneous * Brought Resource Type and Property Type functions up to current spec sheet.
…ions ## 2.9.1 - 2019-09-09 * [Issue #61](#61) -- _Thanks, [@ScriptAutomate](https://github.com/ScriptAutomate)!_ * Updated Synopsis and Description for all Resource Type and Property Type functions to include the information from the parsed documentation.
Just tested, and looks exactly as expected with the latest PowerShell Gallery version based on my above examples:
Closing :) |
Awesome!!! Thanks again! ❤️ |
I was playing around with a similar idea of auto-generating a PowerShell module like this before in the past, and while revisiting it I saw that you've already done a ton of work. This is a feature request with example code in case it would be helpful since my code is going unused.
My pipeline, for function generation, initially did the following:
awsdocs/aws-cloudformation-user-guide/doc_source
has the same name as the HTML endpoints of theDocumentation
property URLs in theCloudFormationResourceSpecification.json
- the extension only needs to be changed to.md
SYNOPSIS
: As you currently are doingDESCRIPTION
:SYNOPSIS
info, plus all paragraphs of the official aws help doc beforeSyntax
markdown header.PARAMETER
descriptions from official aws help docThe results for
PARAMETER
descriptions could accompany the current inclusions ofPrimitiveType
,Documentation
, andUpdateType
.Required
is unnecessary to include since PowerShell is already checking whether[parameter(Mandatory = $true)]
is present, which results inRequired?
output beingtrue
orfalse
.New-VSAlexaAskSkill Example
Differences in help documentation output could look like this, using
New-VSAlexaAskSkill
as an example.Documentation
: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-ask-skill.htmlParameter Information (Current)
Parameter Information (Expanded)
Includes parsed data from Alexa::ASK::Skill
Description Information (Current)
Description Information (Expanded)
Includes parsed data from Alexa::ASK::Skill
I created some sloppy code here that goes through and generates objects with help documentation contents, which is what my module originally used: PowerShell Helpers Proof-of-Concept for Comment-Based Help Generation via Parsing of AWS CFN UserGuide GitHub Docs
If this seems like a welcome feature to be added to this module, I hope the code / method works.
The text was updated successfully, but these errors were encountered: