Take advantage of structured data storage

[EdLichtman]

To be scalable this should create a json file for function and alias with

{
Imports,
InnerText,
Name,
IsExportedMember,
???
}

When I edit function it should generate Import-ModulePrivateScript statements for the array of imports,
Generate the same for any possible imports but commented out, generate $IsExportingMember as text, generate function inside scriptblock, etc.

All of the generated code will allow the function to be run as is and when editing is finished it should regenerate the function based off the configuration. Importing the functions will import all the structured json files.

[EdLichtman]

Module will have module.spec.json and that will host all the functions. Then we don't have to check functions and aliases folders for file names. Additionally copying a function will be as easy as pulling the spec and duplicating it via another key. That's also how we can easily revert edits to function versions. We'll have a revision property

[EdLichtman]

The $modulename.cli.spec.json could also have an easily modifiable $modulename.cli.manifest.json that hosts the common manifest properties and a .cli.releasenotes.json which hosts the private data by a more human readable name

[EdLichtman]

And of course a cli.config.json to host the module configuration like exportRoot, exportModules, name.

This does call into question perhaps a cli.privatespec.json that hosts importable files, that way I can keep the config at modulerootfolder/configs/modules.

Another thing I can do is cli.tests.json so that while you're editing the function you can literally bigdog the tests.

Imagine - a file that reads

Import-ModulePrivateScript 'scriptname'
#Import-ModulePrivateScript 'other-nonimportedname'

Prepare-ModuleFunction (-scriptblock) {
#your code here
}

Run-ModuleTests (-scriptblock) {
describe 'command-name' {
    It 'does something's {

    }
}
}
$isExportingMember = $true

And then we should be able to do the same for private scripts.

[EdLichtman]

I need to learn how to use plaster instead and instead of using json I'll leverage building a template in plaster then creating that template