Carl Ansley
Carl Ansley
One other thing: I haven't tested this, but I assume this issue affects other `Object.prototype` methods like `valueOf`, `toLocaleString`, etc.
FYI for those using it, code coverage support for `node:test` has been back-ported to Node 18.15.0.
Another bump for this feature request, with Node 20 (released today) the test runner is now marked as stable. https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V20.md#20.0.0
WebStorm has support for the native Node test runner now: https://blog.jetbrains.com/webstorm/2023/12/webstorm-2023-3/#new_functionality_for_testing We would very much prefer to use this (vs jest). I hope Jetbrains support for this feature is a...
Sorry it's been a while since I looked at this, are you done with this?
@linusnorton if the PR can be updated to resolve the remaining issue(s) happy to merge it. We have an internal replacement for swagger2 that supports openapi 3 and also external...
We should definitely support this, PRs welcome :)
Would appreciate a PR with this change plus a unit test! Thanks.
Hi thanks for the PR. Can you talk a little about your use case, assume it's CORS related? I'm not entirely clear on why we should treat the OPTION verb...
I suppose it comes down to the "unnecessary boilerplate" thing. I agree it's annoying, but if you're also using your swagger with something like API Gateway you can't get around...