Include a pointer where the error is when the spec is not readable by the form editor

jhordies commented 1 year ago

Is there an existing issue for this?

[X] I have searched the tracker for existing similar issues and I know that duplicates will be closed

Describe the Issue

I had to merge the open api spec with an updated version manually in the code editor. I had to go to https://apitools.dev/swagger-parser/online/ to find what the problem was.

Steps To Reproduce

Mess up the code of a spec. Commit your changes. Go to the form editor --> no usable anymore

Screenshots or Videos

No response

Browser

Chrome

Additional Context?

No response

apigitlabs commented 1 year ago

thanks @jhordies, it is in our road map, but it may take a while to do it well. For better experience, team just added a quick improvement that when the API Spec can't be rendered in "form" viewer, then we automatically switch to "swagger-ui" viewer.

jhordies commented 1 year ago

Thanks!

On Tue, 14 Feb 2023, 22:04 APIGIT, @.***> wrote:

thanks @jhordies https://github.com/jhordies, it is in our road map, but it may take a while to do it well. For better experience, team just added a quick improvement that when the API Spec can't be rendered in "form" viewer, then we automatically switch to "swagger-ui" viewer.

— Reply to this email directly, view it on GitHub https://github.com/apigitlabs/apigit-support/issues/9#issuecomment-1430375702, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB46GWOHGH5MA4W36SYOB3DWXPXNTANCNFSM6AAAAAAU2KJH34 . You are receiving this because you were mentioned.Message ID: @.***>

apigitlabs / apigit-support