Express Server Generation #3
Open
Conversation
This file contains 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
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.
This adds support for Express server generation. To keep it generic, it currently only generates a router that can be plugged into any Express app. The current direction would be to have any
index.jsor app setup files either maintained by hand, or generated by a local doctor-swag plugin.The generator is pretty opinionated on the
handlersmodule in the fact that you must create a handlers module at the top level for the router file to call into. the goal is to divorce the code you would write in a handler and change it into a more generic function that takes input and produces output. All of the Express mechanics would be either generated or handled in the middleware.