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
Thanks for the detailed bug report! This is a bug in our type inference system, where it was relying on parameter names to be exposed as .name, which is not true for parameters with default values. I'm rolling a fix in #239 and will publish it in the next patch release.
On a related note, this code demonstrates something a little tricky: we will infer the default value in the parameter declaration from the code, but specifying a parameter type like {number} overrides this: parameter types are either declared explicitly or inferred. I'm not sure about combining inferred and explicit type information, because it could quickly get complex.
It looks like a bug in any output format when using default argument value in JavaScript
output html

output JSON
The text was updated successfully, but these errors were encountered: