Standard for PowerShell Module Source Repo Layout? #26873
Replies: 2 comments 1 reply
-
|
This sounds like a great community project. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
@sierja Plaster & Sampler (which uses Plaster under the hood) are what I'd say to be what is seen to be a community accepted standards for script module layouts & has some of this already included
You also probably want to look into ModuleBuilder too As such I don't think there's much more desire in the wider community to attempt with building a new "standard" but extending these ones further. I'd also recommend looking at some of the videos on Youtube that reference these modules at various PowerShell Conferences over the years. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As far as I’m aware, there isn’t a standard for how to structure the source of a PowerShell script (as opposed to binary) module in a repository. I’m not talking about the on-disk layout after installation, but rather how module source should be organised during development in a way that works nicely with tooling. I’ve seen a number of informal conventions across different projects, but nothing that feels like a consistent community standard.
Is there interest in defining a standard repository layout for PowerShell script modules, along with build/collation tooling to turn a standardised repo into publish-ready .psm1 and .psd1 files? I’m interested in developing a standard and building the tooling if there’s appetite for it.
Beta Was this translation helpful? Give feedback.
All reactions