-
Notifications
You must be signed in to change notification settings - Fork 88
Simplify the code a bit using async/await #159
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
Merged
Merged
+100
−91
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Hey, I’m cool with it as long as no impact on performance, see the load tests to confirm any issues |
Also, maybe bump the major version as this might break old versions of node, thanks for supporting this by the way, much appreciated |
Tried running the load tests with node.js 16.14.2 before and after applying this change: Before
After
|
Released in 4.0.0 🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've had a bit of trouble wrapping my head around exactly what's going on in
index.js
. Adoptingasync
/await
seems to help a bit. Added some drive-by optimizations as well so more stuff is precomputed outside the middleware itself.This makes the middleware function
async
, but it doesn't ever return a rejected promise because its body is wrapped in a try/catch. This should still be compatible with both vanillaexpress
andexpress-promise-router
.Drive-by fixes #153
@AndrewKeig, this is a bit of an invasive refactoring, so I would appreciate a sign-off from you 😬 🤞