You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 25, 2020. It is now read-only.
When I attempt to regenerate the swagger API from the root directory of my project, it goes through the questionaire/wizard and stubs a new application underneath the root of my project...
e.g.
$ cd /my_project
$ yo swaggerize --only=handlers,models,tests --framework express --apiPath config/api.json
Swaggerize Generator
Tell us a bit about your application
? What would you like to call this project: My Project
? Your name: Derek Brooks
? Your github user name: debrooks
? Your email: debrooks@paypal.com
create .eslintignore
create .eslintrc
create .npmignore
create package.json
create README.md
create server.js
create tests/sample.js
create handlers/sample.js
create data/mockgen.js
create data/sample.js
...
$ ls -l
config
handlers
index.js
My Project
node_modules
package.json
README.md
tests
Notice: in my root directory, ran swaggerize, a new subfolder called My Project exists with all of the newly generated files. I expected it to just generate the missing files based on the swagger api in my current working directory.
When I attempt to regenerate the swagger API from the root directory of my project, it goes through the questionaire/wizard and stubs a new application underneath the root of my project...
e.g.
Notice: in my root directory, ran
swaggerize, a new subfolder calledMy Projectexists with all of the newly generated files. I expected it to just generate the missing files based on the swagger api in my current working directory.