[http-server-js][Bug]: wrong value for optional query parameters

[benjlevesque]

Describe the bug

When using http-server-js, the runtime values of query parameters is not what is described by the type.

In the case of a number, the default value is NaN where it should be undefined.
In the case of a boolean, the default value is false, where it should be undefined.

Reproduction

Here is a repo with the reproduction of each case https://github.com/benjlevesque/repro-typespec-issues/

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[witemple-msft]

Thank you for reporting this oversight and including a repro. This would also cause problems for TypeSpec types that have strict parsers (it's kind of an accident that we don't get a type error here because the Boolean and Number global functions accept undefined as an input). I think it's sufficient for the generator to just check if the property is optional and emit something like param !== undefined ? parse(param) : undefined instead of always emitting parse(param).