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
When expanding the test.TestElement_with_OneOfArray, there are errors in the JavaScript-Console. 'f is undefined'. When removing the 'test.attributeWithTypeSuperElement_Bottom' from test.ABC_SuperElement, everything works fine.
To reproduce...
Steps to reproduce the behavior:
Go to editor.swagger.io
Rightclick somewhere and open the JavaScript-Console displaying on the bottom of the page
Enter the YAML above
Try opening everything else than test.TestElement_with_OneOfArray -> should work fine
Expand test.TestElement_with_OneOfArray
See error:
In Firefox:
TypeError: "f is undefined"
c http://editor.swagger.io/dist/swagger-editor-bundle.js:40
...
Strangely the stacktrace looked a bit different when I tried it a the first times. And the error also looks a bit different when trying it in the other browsers.
For trying it without the from me suspected attribute, remove this from the specification:
test.attributeWithTypeSuperElement_Bottom:
oneOf:
- $ref: '#/components/schemas/test.SubElement_Bottom'
- $ref: '#/components/schemas/test.SubElement_Bottom2'
Refresh the page (otherwise there would be something in the cache and errors wilss come, that won't come when refreshing the page
File -> Clear editor,
File -> Import file for importing the new file without these lines.
Try it again -> Expand test.TestElement_with_OneOfArray
An additional question would be, why the oneOf's in the Array-Items are displayed with the names of the referenced subtypes while the oneOf's in the test.attributeWithTypeSuperElement_Bottom when expanding the attributes further, are displayed with the name of the SuperElement.
The big problem is, that this is just a very minimized spec. In the spec I have to use, there are up to 20k lines and it crashes the browser with these JS-Errors. (With only one as here the displaying is quite what we expected. Except of the difference just explained)
Additional context or thoughts
Can you help me with this? At least telling me if it is a bug and you can solve it or if I did anything wrong?
Thank you very much
The text was updated successfully, but these errors were encountered:
This seems to be related to #5435 and #5705, because the errors in Chrome look the same to me. Just this here is a bit more minimized YAML-Version of a spec.
Q&A (please complete the following information)
Content & configuration
Example Swagger/OpenAPI definition:
Describe the bug you're encountering
When expanding the test.TestElement_with_OneOfArray, there are errors in the JavaScript-Console. 'f is undefined'. When removing the 'test.attributeWithTypeSuperElement_Bottom' from test.ABC_SuperElement, everything works fine.
To reproduce...
Steps to reproduce the behavior:
In Firefox:
TypeError: "f is undefined"
c http://editor.swagger.io/dist/swagger-editor-bundle.js:40
...
Strangely the stacktrace looked a bit different when I tried it a the first times. And the error also looks a bit different when trying it in the other browsers.
test.attributeWithTypeSuperElement_Bottom:
oneOf:
- $ref: '#/components/schemas/test.SubElement_Bottom'
- $ref: '#/components/schemas/test.SubElement_Bottom2'
Additional context or thoughts
Can you help me with this? At least telling me if it is a bug and you can solve it or if I did anything wrong?
Thank you very much
The text was updated successfully, but these errors were encountered: