-
Notifications
You must be signed in to change notification settings - Fork 4k
Adding aliases to a few cmdlets and updating help documentation to match #4110
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akromm I believe you will need to add the aliases (and mapping to corresponding cmdlets) in the following files:
@cormacpayne I'm only adding aliases to cmdlet parameters and not to any cmdlet name. Is it still required to modify those files (there is no cmdlet mapping)? |
I mixed up cmdlet and parameter aliases - ignore my previous comment
@@ -8,7 +8,7 @@ Locale: en-US | |||
|
|||
# AzureRM.Sql Module | |||
## Description | |||
This topic displays help topics for the [Azure SQL Database](https://docs.microsoft.com/azure/sql-database/) Cmdlets. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akromm I think this was a change that was recently made. Do we want to revert it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, thank you for catching. Where is the source for this comment? I'd like to change it at the source so that future re-generation of this file doesn't cause this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akromm I was under the impression that this was the source. Do you remember the command you used to regenerate the markdown help?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cormacpayne I used platyPS:
$pathToHelpFolder = "E:\git\azure-powershell\src\ResourceManager\Sql\Commands.Sql\help"
Update-MarkdownHelpModule -Path $PathToHelpFolder -RefreshModulePage -AlphabeticParamsOrder
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akromm that's the correct command. I would assume this is an issue with how platyPS
parses the markdown (maybe it can't handle links?). I can investigate myself and open an issue in their repository if necessary.
@@ -169,7 +169,7 @@ Specifies the maximum size of the database in bytes. | |||
```yaml | |||
Type: Int64 | |||
Parameter Sets: (All) | |||
Aliases: | |||
Aliases: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: remove?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is auto generated so I'd rather leave it.
100 DTUs | ||
- Premium. | ||
125 DTUs | ||
For the current preview, the edition must be Standard. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
obsolete comment? we have basic and premium edition pools now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have removed this.
### CommonParameters | ||
|
||
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216). | ||
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see about_CommonParameters (http://go.microsoft.com/fwlink/?LinkID=113216). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cormacpayne how do I make the generated markdown include the missing '[' and ']' ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akromm it does not appear to be platyPS
intention to have the brackets around the link: https://github.com/PowerShell/platyPS/blob/b0c97c9de267d9ca46bfef17610a92648efa5069/src/Markdown.MAML/Resources/MarkdownStrings.resx#L175
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akromm I'd have to look, but I think a previously opened PR made the change to wrap the about_CommonParameters
text in the '[' and ']' brackets
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@cormacpayne correct, a previous PR added in the enclosed brackets to make the text a link. I would like to keep it that way during future re-generation of the doc files.
What are your thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@akromm I agree, it would make it much nicer to view in markdown. I can also talk to the platyPS
team about how we can prevent this from getting overridden in the future, since it seems to be a hard-coded string that they use for when a cmdlet uses the above set of verbs.
Description
This checklist is used to make sure that common guidelines for a pull request are followed. You can find a more complete discussion of PowerShell cmdlet best practices here.
General Guidelines
Testing Guidelines
Cmdlet Signature Guidelines
ShouldProcess
and haveSupportShouldProcess=true
specified in the cmdlet attribute. You can find more information onShouldProcess
here.OutputType
attribute if any output is produced - if the cmdlet produces no output, it should implement aPassThru
parameter.Cmdlet Parameter Guidelines