You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The isJsonMime function isn't found in your API documentation anywhere. However, I'm finding that it is a required field in the Configuration type. When trying to build a Configuration object like so:
I am presented with the following Typescript error:
Peering into configuration.d.ts that comes with the package, I see:
exportdeclareclassConfiguration{/** * parameter for apiKey security * @param name security name * @memberof Configuration */apiKey?: string|Promise<string>|((name: string)=>string)|((name: string)=>Promise<string>);
....constructor(param?: ConfigurationParameters);/** * Check if the given MIME is a JSON MIME. * JSON MIME examples: * application/json * application/json; charset=UTF8 * APPLICATION/JSON * application/vnd.company+json * @param mime - MIME (Multipurpose Internet Mail Extensions) * @return True if the given MIME is JSON, false otherwise. */isJsonMime(mime: string): boolean;}
Wondering if this may have slipped into the OpenAPI spec generation by accident. Or if it is required, could you please add it to your documentation?
Thanks,
Steven Chien
The text was updated successfully, but these errors were encountered:
Hey @stevenwchien, have you tried building the config object using its constructor? That's the recommended way to initialize it before making requests with this SDK.
The
isJsonMime
function isn't found in your API documentation anywhere. However, I'm finding that it is a required field in theConfiguration
type. When trying to build aConfiguration
object like so:I am presented with the following Typescript error:
Peering into
configuration.d.ts
that comes with the package, I see:Wondering if this may have slipped into the OpenAPI spec generation by accident. Or if it is required, could you please add it to your documentation?
Thanks,
Steven Chien
The text was updated successfully, but these errors were encountered: