-
-
Notifications
You must be signed in to change notification settings - Fork 172
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
next function in single function case #77
Comments
Hey, sure, this was intentional (initially). Every endpoint should include its own termination. That said, this has already been fixed in the next version of Polka (not yet released) because I realized the inconsistency here. I'll leave this open for tracking purposes while I get 1.0 together. Thanks! |
Thanks for quick reply, any ETA when |
No problem~ 1.0 will be released early January. I'll be polishing it up over the holidays. The code is not public yet as it exists/has been developed within personal projects |
@lukeed any updates on 1.0? |
The core for 1.0 is complete. I'm now just working on supporting packages / middleware. The biggest of them, for illustration, is attaching view engine(s) to your application on command. Express has it built-in, so this will be one of the few remaining differences. I hope to do a very short |
- very unlikely in real-world scenarios - Closes #77
I'm not sure, was such issue raised before or not, I tried search, but did not found.
Why
next
function is not provided if route have only 1 function?polka/packages/polka/index.js
Line 92 in e7aa451
Is not right code will be:
The text was updated successfully, but these errors were encountered: