Skip to content

Formalizing Command Types #452

Closed
Closed

Description

@StartAutomating

As PipeScript grows, so too do the number of specialized types of scripts.

As this is a paradigm we are trying to encourage, it makes sense to formalize it and create a few key reusable pieces.

A Module's Manifest may contain a .CommandType(s) in its PrivateData or PrivateData/PSData section.

The key will be the name of the command type.

The value will be either a pattern for the command's name or a hashtable containing a detailed pattern definition (including .Synopsis/.Description/.Pattern/.PSTypeName)

Much like we can discover a module's relationships (#105) and exports (#104), we should also be able to get [ModuleCommandTypes()]

Activity

  1. added a commit that references this issue on Jun 12, 2023
    77a6f34
  2. added a commit that references this issue on Jun 12, 2023
    787d36d
  3. added a commit that references this issue on Jun 13, 2023
    1784cdf
  4. added 4 commits that reference this issue on Jun 13, 2023
    94b5c5b
    70c6bd9
    e0046f0
    603e5cd
  5. 66 remaining items

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

enhancementNew feature or request

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions