-
Notifications
You must be signed in to change notification settings - Fork 5.6k
fix: serve handler error with 0 arguments #23652
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. I'm OK to merge this, but it's unlikely that a user would realistically write a handler with no arguments and this helps avoid cases where a fetch
export sets off a false positive for our deno serve
hint message. If we're good with that tradeoff, we can merge it. :)
@@ -0,0 +1,5 @@ | |||
{ | |||
"args": "serve --port 12345 main.ts", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does deno serve
find an open port? Maybe we should exclude it from the test? This port conflicts with another test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a way to pick to an open port here? deno serve
doesn't find an open port.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should fix it #23846
Co-authored-by: Satya Rohith <[email protected]> Signed-off-by: Marvin Hagemeister <[email protected]>
Fixes #23651 Co-authored-by: Satya Rohith <[email protected]>
Fixes #23651 Co-authored-by: Satya Rohith <[email protected]>
Fixes #23651