Feature: IoC container

[oscar60310]

This PR added Inversify as our inversion of control (IoC) container, followed by some necessary changes.

1. IoC containers.
   • src/containers - TYPES symbol list, wrapped container, and modules.
   • src/options - Opions classes
2. Path alias
   All path alias have been moved to root tsconfig. But there will be some issues after building projects.
3. Use a facade class instead of pipeline module

[kokokuo]

Great for using IoC, besides some questions and suggestion, others LGTM 👍

[kokokuo]

How about adding the comment to make the members know the source name is the schema file name or rename it to schemaFileName or fileName ?

Because sourceName may not easy to know where the source from, even we could know the templateSource will be assigned the source name if not foundtemplateSource in getTemapleteSource middleware, we still do not know where the default source name from.

And also, even though we found the sourceName is from name field in the SchemaData, the name is a general word ( maybe we could also rename the name in the SchemaData or just also add a comment ) until we see the code of readSchema in the FileSchemaReader, however, it may spend some time to trace.

[oscar60310]

I changed these two properties to "sourceName" and added some comments about them.

export interface RawAPISchema extends DeepPartial<Omit<APISchema, 'request'>> {
  /** Indicate the identifier of this schema from the source, it might be uuid, file path, url ...etc, depend on the provider */
  sourceName: string;
  request?: DeepPartial<RawRequestParameter[]>;
}

export interface SchemaData {
  /** The identifier of this schema, we might use this name to mapping SQL sources. */
  sourceName: string;
  content: string;
  type: SchemaFormat;
}

The sourceName here indicated the identifier of the schema, it might be file path (File provider), URL (s3 provider), UUID (database provider) ...etc. in the future, so I didn't rename it the schemaFileName or fileName.

[kokokuo]

Thanks for telling me the sourceName purpose in the future, thanks, no problem and thanks for you comment added 👍

[kokokuo]

Why rename to schemaPath ?
Actually I think folderPath is good because the folderPath could let us know the path is the folder, however, the schemaPath may not know the path is a file or folder until we saw the code in FileSchemaReader .

If you would like to let member know the path is the shcema folder path, maybe you could just name schemaFolderPath (although it may be a little long, but could be clear I think, how do think ? )

[oscar60310]

Both schemaPath and templatePath have been renamed to folderPath, thanks!

[kokokuo]

Also please rebase develop branch, thanks ~

[oscar60310]

Hi @kokokuo , I've rebased the branch and fixed the issues.

[kokokuo]

It has been checked, No Problem, thanks for replying to me 👍