-
Notifications
You must be signed in to change notification settings - Fork 48
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
Unable to load SwaggerUI #58
Comments
Managed to fix the above but now the UI in Swagger tab remains the same even after importing the http In node.. Swagger UI remains same even after trying various combinations of the http node. Below is my node flow: [{"id":"ac44da7e.5b7d38","type":"http in","z":"952022f4.3bcd9","name":"","url":"/test","method":"get","upload":false,"swaggerDoc":"4974c96.827c438","x":320,"y":140,"wires":[["2768f500.667aec","d33b2e0.5b574d"]]},{"id":"4974c96.827c438","type":"swagger-doc","z":"952022f4.3bcd9","summary":"testing the swagger node","description":"test","tags":"testingTags","consumes":"/test","produces":"/result","parameters":[{"name":"itemNum","in":"query","description":"the item's identifier","required":false,"type":"integer"}],"responses":{"200":{"description":"200 action","schema":{"properties":{"200 action":{"type":"string","name":"200 action","propertyRow":true}}},"code":"200"},"400":{"description":"the request was malform","schema":{"properties":{"Error":{"type":"string","name":"Error","propertyRow":true}}},"code":"400"}},"deprecated":false}] Node Red , Swagger UI Screengrab: Swagger.json screengrabs: |
Hey FaizulHassan, Any chance you got it fixed, I'm having the exact same issue :/ Regards, |
#67 has been merged that should address this issue - version 0.1.9 of the node published to npm. |
Hi , I tried implementing Swagger following your instructions.
I have it installed correctly but my swagger.json throws the following error..
In the developer console I get the log as below:
Node-Red Log:
Node Structure:
.node-red -->
node_module -->
Please help fix my problem..
Thank You!
The text was updated successfully, but these errors were encountered: