-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Write new guide on creating middleware for use with Express #461
Comments
@ritch Is this sufficient for the time being? Do you think we should expand on the above article or can we close this issue? |
I think we can go a bit deeper. This looks like an introduction to writing middleware. Thinking from the perspective of a new middleware author I want to know the common patterns, things to avoid, etc. This is a good start but I think we are missing quite a bit. |
@ritch what I can think of adding further is explaining "requireable" middleware, common module patterns, Do you think we should cover publishing to npm as well? |
@hacksparrow let's chat in realtime about this. I think what you're suggesting is still a little too light. Maybe we need to split this into several guides this being the first. |
@ritch I send you a mail. |
@ritch If you still think we need more here, please advise. |
@ritch @hacksparrow @crandmck what's the status of this story? It has been sitting in #review column for 20 days by now. Can we close it as done? |
@hacksparrow thank you for the update, makes sense. I'll move this story back to |
@hacksparrow I reassigned back to you based on above comments. If you have anything (even a draft) written up, please share it, either in a branch or in the wiki. Then I can take it, if you have other priorities. |
I'm going to go ahead and close this issue. If someone wants to add specifics as to what more we want to add to the site, please open a new issue. |
Per discussion and #454.
The text was updated successfully, but these errors were encountered: