Support absolute paths to generators in the forge command

[ms14981]

Tried to run the following command (on Git Bash):

openapi-forge forge <schema> C:\dev\open-api-forge\openapi-forge-java-initial

It gives the error:

<path>\openapi-forge\src\common\generatorResolver.js:36
    throw new Error(
          ^

Error: Generator URL C:devopen-api-forgeopenapi-forge-java-initial does not end with ".git", check that the URL points to a valid generator

There are a couple of things to consider here:

• Will it be ambiguous whether a given argument is a relative path, an absolute path or a URL?
• Does the schema argument support absolute paths? If not, should it?
• Do the other commands support absolute paths? If not, should they?

[gkocak-scottlogic]

Absolute paths works fine on unix environments.

node src/index.js forge <schema> /home/X/repos/openapi-forge-java-initial/ -o ...

runs without issues.

About the windows side of things, my guess is fs.existsSync on windows native directories in git-bash doesn't get validated correctly maybe. For the git error part, the path is still validated as an URL which triggers that as a git repo automatically to be fetched with git.

[ms14981]

Testing the schema argument, looks like that doesn't work with absolute paths either:

openapi-forge forge C:/dev/open-api-forge/openapi-forge-java-initial/features/schema.json  https://github.com/ScottLogic/openapi-forge-typescript.git

We get this error (from node-fetch?): "Only absolute URLs are supported"