-
Notifications
You must be signed in to change notification settings - Fork 33
Update links in README to use editor-next.swagger.io & update reference to CAMARA API Guideline #327
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
Update links in README to use editor-next.swagger.io & update reference to CAMARA API Guideline #327
Conversation
The PR is fine for me, but I have not the impression that using the next-editor from Swagger is a general solution. |
@hdamker on our side at DT, some of us faced the issue, that the "normal" editor.swagger.io was not working as expected anymore. But I can also investigate or we can try to find a general solution in Commonalities. |
I might fit better into Tooling, have created camaraproject/tooling#8 as a start. And yes, the problem was observed by others as well. With the now merged links it looks for me like this - left panel is not loading the code: |
Oh ... okay. |
@hdamker maybe this is an issue on swagger editor, why I changed it to editor-next. swagger-api/swagger-editor#5484 That's why I changed it to editor-next. |
It was mentioned in some meetings and e.g. here: https://camara-project.slack.com/archives/C05SH6QDWP7/p1745834520529549. I hoped that is a temporary problem. |
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
Changes the usage of viewing Swagger-UI via editor-next.swagger.io
Fixes #325