const data = None; in client/USAGE.md

[yeldarby]

Several places in this doc there's a pattern to do this:

const data = None;
request.body = data;

This pattern seems like bad practice and it's unclear what it's supposed to mean/be doing.

It appears to signify when you're not to be passing a body to the API endpoint. In most cases None is likely to be undefined. But it's not a reserved word or magic value in JavaScript and may be set to a value other than undefined elsewhere in a codebase code which may produce unexpected side effects.

[thinkingserious]

Thanks for bringing this to our attention @yeldarby. I think this is a bug in our auto-generation code, since that particular file is auto-generated from our OpenAPI spec.

I'm leaving this open for a fix on our end, but we would also appreciate a manual PR if someone has the time to do that before it bubbles up on our backlog.

With Best Regards,

Elmer