Undefined is not the same as falsy

[mbursill]

There's an undefined check on route arguments but it's not actually checking for undefined:

This causes an issue if the value is anything that would return falsy (0, empty string, false).

[baywet]

Hi @mbursill,
Thanks for using kiota and for reaching out.
I've transferred your issue to the main generation repository.
First off, heads up, with the upcoming version of kiota, the generated code in TypeScript is changing significantly.
The API surface for the application will remain the same, but the fluent API surface moving from classes to interfaces + proxy + constants to significantly reduce the bundle size. (~44%)
You can try this by using the recent pre-release (make sure you update your kiota dependencies as well)

Lastly, the code that emits that check, is located here in case you'd like to submit a pull request.

kiota/src/Kiota.Builder/Writers/TypeScript/CodeFunctionWriter.cs

Line 275 in eb6c755

writer.WriteLine($"if(!{parameterName}) throw new Error(\"{parameterName} cannot be undefined\");");