You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See screenshot. Some (but not all!) of our specs have strange syntax highlighting, and I cannot figure out what is causing it. In the screenshot above, you can see the request body changes colors all over the place but the response does not. The spec being used in the example above is 3.0.3. We are using swagger-ui-react v.3.46.0.
I've seen some other issues about this, but not much in the way to how to fix it. I'm not sure if this is a bug or something we're doing wrong on our end. The specs we're using are valid. Some are 2.0 and others are 3.0.x. I cannot give out access to our site, unfortunately.
Expected behavior
Syntax highlighting should be consistent across request and response bodies.
The text was updated successfully, but these errors were encountered:
@jaydreyer could you describe the main differences between the specs that are having wrong behavior vs those that work correctly.
I have tried some things but I could not reproduce this with the specs I have tried:
Q&A (please complete the following information)
Content & configuration
Describe the bug you're encountering
See screenshot. Some (but not all!) of our specs have strange syntax highlighting, and I cannot figure out what is causing it. In the screenshot above, you can see the request body changes colors all over the place but the response does not. The spec being used in the example above is 3.0.3. We are using swagger-ui-react v.3.46.0.
I've seen some other issues about this, but not much in the way to how to fix it. I'm not sure if this is a bug or something we're doing wrong on our end. The specs we're using are valid. Some are 2.0 and others are 3.0.x. I cannot give out access to our site, unfortunately.
Expected behavior
Syntax highlighting should be consistent across request and response bodies.
The text was updated successfully, but these errors were encountered: