Skip to content

Formalizing Command Types #452

Closed
Closed
@StartAutomating

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()]

Metadata

Metadata

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions