Skip to content

Refactor: Get-PSakeScriptTasks#324

Merged
HeyItsGilbert merged 1 commit intopsake:masterfrom
Splaxi:refactor-psgettaskscripttask
Sep 21, 2024
Merged

Refactor: Get-PSakeScriptTasks#324
HeyItsGilbert merged 1 commit intopsake:masterfrom
Splaxi:refactor-psgettaskscripttask

Conversation

@Splaxi
Copy link
Copy Markdown
Contributor

@Splaxi Splaxi commented Apr 14, 2022

Convert parameter names into pascal

Description

Convert parameter names into pascal

Related Issue

#308

Motivation and Context

How Has This Been Tested?

ps>Get-Help Get-PSakeScriptTasks -Full

NAME
    Get-PSakeScriptTasks

SYNOPSIS
    Returns meta data about all the tasks defined in the provided psake script.


SYNTAX
    Get-PSakeScriptTasks [[-BuildFile] <String>] [<CommonParameters>]


DESCRIPTION
    Returns meta data about all the tasks defined in the provided psake script.


PARAMETERS
    -BuildFile <String>
        The path to the psake build script to read the tasks from.

        Required?                    false
        Position?                    1
        Default value
        Accept pipeline input?       false
        Accept wildcard characters?  false

    <CommonParameters>
        This cmdlet supports the common parameters: Verbose, Debug,
        ErrorAction, ErrorVariable, WarningAction, WarningVariable,
        OutBuffer, PipelineVariable, and OutVariable. For more information, see
        about_CommonParameters (https:/go.microsoft.com/fwlink/?LinkID=113216).

INPUTS

OUTPUTS

    -------------------------- EXAMPLE 1 --------------------------

    PS C:\>Get-PSakeScriptTasks -BuildFile '.\build.ps1'

    DependsOn        Alias Name    Description
    ---------        ----- ----    -----------
    {}                     Compile
    {}                     Clean
    {Test}                 Default
    {Clean, Compile}       Test

    Gets the psake tasks contained in the 'build.ps1' file.





RELATED LINKS
    Invoke-psake

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@HeyItsGilbert HeyItsGilbert merged commit ab8afbd into psake:master Sep 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants