Oapi Generate
[INTERNAL] Generate Beamable client source code from open API documents
beam oapi generate [options]
About
[INTERNAL] Generate Beamable client source code from open API documents
Options
Name | Type | Description |
---|---|---|
--concat | Boolean | When true, all the generated code will be in one file. When false, there will be multiple files |
--output | String | When null or empty, the generated code will be sent to standard-out. When there is a output value, the file or files will be written to the path |
--filter | String | Filter which open apis to generate. An empty string matches everything |
--engine | String | Filter which engine code we should generate (unity |
--conflict-strategy | GenerateSdkConflictResolutionStrategy | When multiple openAPI documents identify a schema with the same name, this flag controls how the conflict is resolved |
--cleaning-strategy | CleaningStrategy | Specifies what should happened with directory output |
--dryrun | Boolean | Should any networking happen? |
--cid | String | Cid to use; will default to whatever is in the file system |
--pid | String | Pid to use; will default to whatever is in the file system |
--quiet | Boolean | When true, skip input waiting and use defaults |
--host | String | The host endpoint for beamable |
--refresh-token | String | Refresh token to use for the requests |
--log | String | Extra logs gets printed out |
--dir | String | Directory to use for configuration |
--raw | Boolean | Output raw JSON to standard out. This happens by default when the command is being piped |
--pretty | Boolean | Output syntax highlighted box text. This happens by default when the command is not piped |
--dotnet-path | String | a custom location for dotnet |
--version | Boolean | Show version information |
--help | Boolean | Show help and usage information |
Parent Command
Updated 6 months ago