Closed jhordies closed 1 year ago
Thank you for your input, @jhordies. After investigating the issue further, we suspect that the JSON in the original specification may have been broken, causing it to be mistakenly interpreted as YAML. We will attempt to reproduce the issue and provide an update as soon as possible.
@jhordies , we can't reproduce it locally, but made some improvement to avoid this case. Can you help to double check and see if it is fixed ?
Hi, thanks, it seems fixed.
On Mon, 10 Apr 2023 at 20:40, APIGIT @.***> wrote:
@jhordies https://github.com/jhordies , we can't reproduce it locally, but made some improvement to avoid this case. Can you help to double check and see if it is fixed ?
— Reply to this email directly, view it on GitHub https://github.com/apigitlabs/apigit-support/issues/14#issuecomment-1502164817, or unsubscribe https://github.com/notifications/unsubscribe-auth/AB46GWPRE6GWJXLMNOR2MJDXARHZXANCNFSM6AAAAAAWOPRPXY . You are receiving this because you were mentioned.Message ID: @.***>
thanks @jhordies for the confirmation , I will close this issue first.
Is there an existing issue for this?
Describe the Issue
While editing a json specification, when using the form editor (to simply add a summary to an operation) if I open the code editor, it became a yaml file
Steps To Reproduce
While editing a json specification, when using the form editor (to simply add a summary to an operation) if I open the code editor, it became a yaml file
Screenshots or Videos
No response
Browser
Chrome
Additional Context?
No response