@accelbyte/codegen 3.1.0 → 4.0.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/PATCHING.md CHANGED
@@ -72,7 +72,7 @@ For example, take a look at the this object
72
72
  }
73
73
  ```
74
74
 
75
- This definition says that `TokenResponseV3` will always give out `xuid`. Yet at the moment, that property shouldn't always appear in the current IAM and the Swagger JSON is mistakenly written that way. If we kept the `xuid` property there, the response validation in the Web SDK will throw error and say the response missed the `xuid` property. Therefore, the JSON Patches are created, and it looks like this
75
+ This definition says that `TokenResponseV3` will always give out `xuid`. Yet at the moment, that property shouldn't always appear in the current IAM and the Swagger JSON is mistakenly written that way. If we kept the `xuid` property there, the response validation in the TypeScript SDK will throw error and say the response missed the `xuid` property. Therefore, the JSON Patches are created, and it looks like this
76
76
 
77
77
  ```
78
78
  {
package/README.md CHANGED
@@ -1,6 +1,6 @@
1
- # AccelByte Web SDK Code Generator
1
+ # AccelByte TypeScript SDK Code Generator
2
2
 
3
- AccelByte Code Generator is a CLI tool that facilitates creating an AccelByte Web SDK from AccelByte OpenAPI definitions.
3
+ AccelByte Code Generator is a CLI tool that facilitates creating an AccelByte TypeScript SDK from AccelByte OpenAPI definitions.
4
4
 
5
5
  ## CLI
6
6
  This codegen build a CLI called `accelbyte-codegen` that will be used to generate code from given config.
@@ -80,7 +80,7 @@ yarn accelbyte-codegen download-swaggers --config ./config.json --swaggersOutput
80
80
  ```
81
81
  *note: please adjust the `--config` flag with the path of config.json file that was already set up before, and please specify the swagger output directory by using `--swaggersOutput` flag.
82
82
 
83
- **Step 6: Generate Code from Swagger Files** after the swagger file has already been downloaded we can proceed to generating Web SDK code from the Swagger File using this command :
83
+ **Step 6: Generate Code from Swagger Files** after the swagger file has already been downloaded we can proceed to generating TypeScript SDK code from the Swagger File using this command :
84
84
  ```
85
85
  npm exec -- accelbyte-codegen generate-code --config ./config.json --swaggersOutput ./swaggers --output ./sdk
86
86
  ```