Created by: YishTish
PR checklist
-
Read the contribution guidelines. -
Ran the shell script under ./bin/to update Petstore sample so that CIs can verify the change. (For instance, only need to run./bin/{LANG}-petstore.sh,./bin/openapi3/{LANG}-petstore.shif updating the {LANG} (e.g. php, ruby, python, etc) code generator or {LANG} client's mustache templates). Windows batch files can be found in.\bin\windows\. If contributing template-only or documentation-only changes which will change sample output, be sure to build the project first. -
Filed the PR against the correct branch: master,4.1.x,5.0.x. Default:master. -
Copied the technical committee to review the pull request if your PR is targeting a particular programming language.
Description of the PR
Changed from parsing, validating, and routing OpenAPI V2 documents to V3. Using a different library for analyzing and parsing. Routing now works all the way from express server to controllers, who collect data based on yaml definition, and then pass to service, which returns stubs according to yaml definition. Please use the /controllers.Pet.js, and /services/petService.js as samples from which to generate automatic code for Codegen. Both these directories are dependent/inherit from a parent Controller.js/Service.js file - this is where the common business logic is written.
Still missing:
- Updated documentation
- Security handling
- Serving different content types, both incoming and outgoing.