Configuration not used within FetchParamCreator

In the generated code example below, the configuration object is not used in the Object.assign statement used to establish the settings for the request.

```typescript
export const PingApiFetchParamCreator = function (configuration?: Configuration) {
return {
/**
*
* @summary Gets the current version information for the application
* @param {*} [options] Override http request option.
* @throws {RequiredError}
*/
get(options: any = {}): FetchArgs {
const localVarPath = `/api/Ping`;
const localVarUrlObj = url.parse(localVarPath, true);
const localVarRequestOptions = Object.assign({ method: 'GET' }, options);
const localVarHeaderParameter = {} as any;
const localVarQueryParameter = {} as any;

localVarUrlObj.query = Object.assign({}, localVarUrlObj.query, localVarQueryParameter, options.query);
// fix override query string Detail: https://stackoverflow.com/a/7517673/1077943
delete localVarUrlObj.search;
localVarRequestOptions.headers = Object.assign({}, localVarHeaderParameter, options.headers);

return {
url: url.format(localVarUrlObj),
options: localVarRequestOptions,
};
}
}
}
```

Start by locating the generator entry point or template that produces PingApiFetchParamCreator and inspect how configuration is handled around the Object.assign statement shown in the issue. Confirm the generated request settings use the provided configuration, then regenerate the TypeScript Fetch API example and verify the resulting code.

Written by the indexing model from the issue text.