nicolaiarocci
commented
7 years ago eve-swagger is designed to work with eve itself and does not know anything about eve-mongoengine. I would say it is a eve-mongoengine issue, wether they want to support eve-swagger or not.
The Eve-Mongoengine is a python library used to import mongoengine models into eve: https://github.com/MongoEngine/eve-mongoengine
I had eve and eve-swagger working together fine. After I tried to install Eve-Mongoengine in my virtualenv, the eve-swagger produced an internal error when I tried to visit /api-docs endpoint. I've realized that there must be some version conflict between eve-swagger and Eve-Mongoengine that makes problems. It's output of eve when I tried to get /api-docs endpoint: 127.0.0.1 - - [28/Aug/2017 10:31:46] "GET /api-docs HTTP/1.1" 500 - I tried eve in DEBUG mode and got nothing.
It's is my requirements.txt file before installing Eve-Mongoengine that was fine: Cerberus==0.9.2 click==6.7 Eve==0.7.4 Eve-Swagger==0.0.7 Events==0.2.2 Flask==0.12 Flask-PyMongo==0.5.1 itsdangerous==0.24 Jinja2==2.9.6 MarkupSafe==0.23 pymongo==3.5.0 simplejson==3.11.1 Werkzeug==0.11.15
This is my requirements.txt after installing Eve-Mongoengine that makes /api-docs unavailable: blinker==1.4 Cerberus==0.7.2 click==6.7 Eve==0.4 Eve-Mongoengine==0.0.9 Eve-Swagger==0.0.7 Events==0.2.1 Flask==0.10.1 Flask-PyMongo==0.3.0 itsdangerous==0.24 Jinja2==2.7.3 MarkupSafe==0.23 mongoengine==0.13.0 pymongo==2.7.1 simplejson==3.5.2 six==1.10.0 Werkzeug==0.9.6
I am going to report this issue in Eve-Mongoengine git project.