Add explicit outputDir options per component

[delaneyj]

Is your feature request related to a problem? Please describe.
While there is outDir in the open-rpc-generator-config.json is still forces the output relative to outDir to be ${type}/${language}.

Describe the solution you'd like

{
  "openrpcDocument": "openrpc.json",
  "outDir": ".",
  "components": [
    {
      "type": "client",
      "name": "@foo/client",
      "language": "typescript",
      "outDir": "../foo-client"
    },
    {
      "type": "server",
      "name": "@foo/server",
      "language": "typescript",
      "outDir": "../foo-server"
    }
  ]
}

Describe alternatives you've considered
Not really, though it ties directly to #624 and possible making the generation more configurable.

Additional context
This is primarily to working well with workspace implementation such as Yarn/Lerna or PNPM.

[zcstarr]

Hey thanks for the suggestion ! I think this makes sense , the behavior of outDir will differ though, so we are going to label the outDir on the component outPath.

Where this time for outPath it will just be absolute path without inference.

The behavior will be as follows

(outDirSpecified, outPathonComponent)

(outDir, null) -> same behavior as current
(outDir,outPath) -> outPath full path specified here is used no directory inference type/language
(null,outPath) -> outPath is used , meaning outDir is optional if all components have outPath
(null, null) -> Not allowed

[openrpc-bastion]

🎉 This issue has been resolved in version 1.22.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀