Feat/template

[Si3rr4wow]

This PR:

• Adds a template to spool up a new patio
• Builds a YAML template from the maintained JSON template and writes both to the bin
• Validates the built templates pre-push
• Replaces the openapi stub file created by feat/wizard with a copy of the relevant template

[Si3rr4wow]

to be removed in a later commit, I just didn't wanna have to run the wizard over and over to test this

[Si3rr4wow]

I sense this would be more testable if I removed the dependency on fs

[robmorgan-tab]

Or you could use one of the many libraries which have this functionality built in. ;)

• klaw or klaw-sync
• fs-extra
• walker
• walk-sync

Then you have no need to write tests for the file system functionality - trust the library :D

[robmorgan-tab]

You could reduce duplication here

const createSubdirectory = (directoryPath: string): void => {
  const directoryName = path.dirname(directoryPath)
  const directoryStats = fs.statSync(directoryName, { throwIfNoEntry: false })
  if (!directoryStats?.isDirectory()) {
    fs.mkdirSync(directoryName)
  }
}

const makeBinTemplateSubdirectories = (jsonPath: string): void => {
  const { jsonBinPath, yamlBinPath } = getBinTargetPaths(jsonPath)
  [jsonBinPath, yamlBinPath].forEach((binPath) => createSubdirectory(binPath))
}

[Si3rr4wow]

So this makeBinTemplateSubdirectories function is one of the things that disappeared one I started refactoring in #15. Turns out what I actually wanted was some conditions around a mkdir so I can use the same function to make the top level bin/templates and the subdirectories.

The forEach has given me the idea for a func that invokes getTemplateFileStrings and getBinTargetPaths and returns an array like { path: string, file: string }[], that should have better handing in writeFileToBin, like

getWritables(jsonPath).forEach(({ path, file }) => {
      makeDirectory(path.dirname(path))
      fileSystem.writeFileSync(path, file)
})

[robmorgan-tab]

Looking really good.
My only thought/suggestion is that when running lay-patio the template directories & OpenAPI root file might be better if placed into a src directory.
That'd avoid the top level getting cluttered with additional tooling as the out of the box project grows.