-
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
Swagger UI not displayed #51
Comments
Hi - what versions of node.js / node-red / node-red-node-swagger ui are you using? You've been using the swagger node for some time. Is this the first time you've tried it on Chrome? |
Hi, The versions I use are I have another project running on the same environment (with Chrome), for which Swagger-UI is displayed correctly. Seems to be a problem in flows file.
So, I tried deleting the flow which is leading to that error, but it did not help much. |
The problem was solved in swagger-ui module |
Please do share the flow file. Is it one you've manually generated somehow? Does it involve subflows? ... ok, I see you've just closed this having manually fixed something... Does that mean there's nothing for us to do? Does this fix need applying somewhere? |
I have created pull request in swagger-ui repository: The flow was edited only with node-red editor. Yes, it contains subflows. Sending by mail. |
Ok, so we better leave this open so we pick up the fixed swagger-ui when it gets resolved. |
Alas this one won't get resolved this way because the |
When loading Node-red UI in chrome, following exception is printed in browser console:
The text was updated successfully, but these errors were encountered: