···1313 - [Linting](#linting)
1414 - [Enums](#enums)
1515 - [Config API](#config-api)
1616+- [Migrating](#migrating)
1617- [Contributing](#contributing)
17181819## About
···160161 -o, --output <value> Output directory (required)
161162 -c, --client <value> HTTP client to generate [fetch, xhr, node, axios, angular] (default: "fetch")
162163 --name <value> Custom client class name
163163- --useOptions <value> Use options instead of arguments (default: false)
164164+ --useOptions <value> Use options instead of arguments (default: true)
164165 --base <value> Manually set base in OpenAPI config instead of inferring from server value
165166 --enums Generate JavaScript objects from enum definitions (default: false)
166167 --exportCore <value> Write core files to disk (default: true)
···178179 --useDateType <value> Output Date instead of string for the format "date-time" in the models (default: false)
179180 -h, --help display help for command
180181```
182182+183183+## Migrating
184184+185185+While we try to avoid breaking changes, sometimes it's unavoidable in order to offer you the latest features.
186186+187187+### v0.27.38
188188+189189+### `useOptions: true`
190190+191191+By default, generated clients will use a single object argument to pass values to API calls. This is a significant change from the previous default of unspecified array of arguments. If migrating your application in one go isn't feasible, we recommend deprecating your old client and generating a new client.
192192+193193+```ts
194194+import { DefaultService } from 'client' // <-- old client with array arguments
195195+196196+import { DefaultService } from 'client_v2' // <-- new client with options argument
197197+```
198198+199199+This way, you can gradually switch over to the new syntax as you update parts of your code. Once you've removed all instances of `client` imports, you can safely delete the old `client` folder and find and replace all `client_v2` calls to `client`.
181200182201## Contributing
183202