You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/StandbyPool/StandbyPool.Autorest/UX/Microsoft.StandbyPool/standbyContainerGroupPools-runtimeViews.json
Copy file name to clipboardExpand all lines: src/StandbyPool/StandbyPool.Autorest/UX/Microsoft.StandbyPool/standbyVirtualMachinePools-runtimeViews.json
Copy file name to clipboardExpand all lines: src/StandbyPool/StandbyPool.Autorest/custom/README.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
# Custom
2
-
This directory contains custom implementation for non-generated cmdlets for the `Az.StandbyPool` module. Both scripts (`.ps1`) and C# files (`.cs`) can be implemented here. They will be used during the build process in `build-module.ps1`, and create cmdlets into the `..\exports` folder. The only generated file into this folder is the `Az.StandbyPool.custom.psm1`. This file should not be modified.
2
+
This directory contains custom implementation for non-generated cmdlets for the `Az.StandbyPool` module. Both scripts (`.ps1`) and C# files (`.cs`) can be implemented here. They will be used during the build process in `build-module.ps1`, and create cmdlets into the `../exports` folder. The only generated file into this folder is the `Az.StandbyPool.custom.psm1`. This file should not be modified.
3
3
4
4
## Info
5
5
- Modifiable: yes
@@ -15,10 +15,10 @@ For C# cmdlets, they are compiled with the rest of the generated low-level cmdle
15
15
For script cmdlets, these are loaded via the `Az.StandbyPool.custom.psm1`. Then, during the build process, this module is loaded and processed in the same manner as the C# cmdlets. The fundamental difference is the script cmdlets use the `ParameterSetName` attribute and C# cmdlets do not. To create a script cmdlet variant of a generated cmdlet, simply decorate all parameters in the script with the new `ParameterSetName` in the `Parameter` attribute. This will appropriately treat each parameter set as a separate variant when processed to be exported during the build.
16
16
17
17
## Purpose
18
-
This allows the modules to have cmdlets that were not defined in the REST specification. It also allows combining logic using generated cmdlets. This is a level of customization beyond what can be done using the [readme configuration options](https://github.com/Azure/autorest/blob/master/docs/powershell/options.md) that are currently available. These custom cmdlets are then referenced by the cmdlets created at build-time in the `..\exports` folder.
18
+
This allows the modules to have cmdlets that were not defined in the REST specification. It also allows combining logic using generated cmdlets. This is a level of customization beyond what can be done using the [readme configuration options](https://github.com/Azure/autorest/blob/master/docs/powershell/options.md) that are currently available. These custom cmdlets are then referenced by the cmdlets created at build-time in the `../exports` folder.
19
19
20
20
## Usage
21
-
The easiest way currently to start developing custom cmdlets is to copy an existing cmdlet. For C# cmdlets, copy one from the `generated/cmdlets` folder. For script cmdlets, build the project using `build-module.ps1` and copy one of the scripts from the `..\exports` folder. After that, if you want to add new parameter sets, follow the guidelines in the `Details` section above. For implementing a new cmdlets, at minimum, please keep these parameters:
21
+
The easiest way currently to start developing custom cmdlets is to copy an existing cmdlet. For C# cmdlets, copy one from the `generated/cmdlets` folder. For script cmdlets, build the project using `build-module.ps1` and copy one of the scripts from the `../exports` folder. After that, if you want to add new parameter sets, follow the guidelines in the `Details` section above. For implementing a new cmdlets, at minimum, please keep these parameters:
22
22
- Break
23
23
- DefaultProfile
24
24
- HttpPipelineAppend
@@ -36,6 +36,6 @@ For processing the cmdlets, we've created some additional attributes:
- Used in C# cmdlets to route exported cmdlets to the `..\internal`, which are *not exposed* by `Az.StandbyPool`. For more information, see [README.md](..\internal/README.md) in the `..\internal` folder.
39
+
- Used in C# cmdlets to route exported cmdlets to the `../internal`, which are *not exposed* by `Az.StandbyPool`. For more information, see [README.md](../internal/README.md) in the `../internal` folder.
This directory contains the documentation of the cmdlets for the `Az.StandbyPool` module. To run documentation generation, use the `generate-help.ps1` script at the root module folder. Files in this folder will *always be overridden on regeneration*. To update documentation examples, please use the `..\examples` folder.
2
+
This directory contains the documentation of the cmdlets for the `Az.StandbyPool` module. To run documentation generation, use the `generate-help.ps1` script at the root module folder. Files in this folder will *always be overridden on regeneration*. To update documentation examples, please use the `../examples` folder.
3
3
4
4
## Info
5
5
- Modifiable: no
@@ -8,4 +8,4 @@ This directory contains the documentation of the cmdlets for the `Az.StandbyPool
8
8
- Packaged: yes
9
9
10
10
## Details
11
-
The process of documentation generation loads `Az.StandbyPool` and analyzes the exported cmdlets from the module. It recognizes the [help comments](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comment_based_help) that are generated into the scripts in the `..\exports` folder. Additionally, when writing custom cmdlets in the `..\custom` folder, you can use the help comments syntax, which decorate the exported scripts at build-time. The documentation examples are taken from the `..\examples` folder.
11
+
The process of documentation generation loads `Az.StandbyPool` and analyzes the exported cmdlets from the module. It recognizes the [help comments](https://learn.microsoft.com/powershell/module/microsoft.powershell.core/about/about_comment_based_help) that are generated into the scripts in the `../exports` folder. Additionally, when writing custom cmdlets in the `../custom` folder, you can use the help comments syntax, which decorate the exported scripts at build-time. The documentation examples are taken from the `../examples` folder.
0 commit comments