Open ponelat opened 6 years ago
Yep, this is us not serializing the Immutable data correctly.
I wrangled something similar in extension value display ahead of v3.5.0 last week, in this commit: https://github.com/swagger-api/swagger-ui/pull/3945/commits/b42e2a7045543429fcaddc782d6103dfbabd2080
i have the same issue,, is there any solution?
@shockey help is needed. Please, look at this issue as soon as possible. Thank you.
There is a workaround for the bug: pass XML you need as a string, e.g. "<tag>Quotes should be \" escaped</tag>"
@bbagno In my application i see this in the models when i add XmlAttribue, XmlElement and XmlType annotations to the properties of the model...
@shockey Can you look at this issue again? :\
FYI: this is still in my work queue!
I'm using springdoc-openapi 1.4.1 and I have this xml-stuff in my swagger-ui too.
Any hint to ignore such internal data?
In my case its the same as @mmamyan wrote. It have something todo with the Xml***annotations,
I generate my classes with jaxb from xsd ... example:
And then I have something like this:
Same problem happens with example
in JSON:
The same, I see example: OrderedMap { ... }
too, in the schema templates. It is annoyed to see the OrderedMap
.
Any update here? Or hints where to look more closely? If so I could try to fix this?
Maybe this here is related to https://github.com/swagger-api/swagger-core/issues/3153 ?
Hi, any update ?
Hi, any updates or ideas how to hide this?
I have this problem too.. is this really still a thing after 4 years??
Hi, I am not sure whether this issue is fixed already , You can disabling skipOperationExample flag during openapi-generator to hide the "example: OrderedMap"
still a problem.
Can this still be the same issue 6 years later? I'm also seeing "orderedMap" in my examples.
same
bump
Someone? we are approaching the '6 year old bug, still not fixed' anniversary day rapidly!!
I'm affected by this, six year old bug.
I don't have this problem anymore. I'm using this stack:
springboot: 3.2.2 springdoc-openapi-starter-webmvc-ui: 2.3.0 springdoc-openapi-starter-webflux-ui: 2.3.0 javax.xml.bind:jaxb-api: 2.3.1 jdk17
I still generate some of my api-objects with jaxb and so there are referenced in my openapi schema ... So from my side everything is fine meanwhile :D
Hey Can you assign this to me? I will try to fix the issue Thank you
Any update on this bug? I'm still seeing OrderedMap in an object example.
Demonstration API definition
petstore.swagger.io ( using its default petstore 2.0 )
Expected Behavior
A UI indicating the XML behaviour that isn't a dump of the underlying immutablejs object. See screencap, look for OrderedMap
Current Behavior
xml: OrderedMap { "name": "photoUrl", "wrapped": true }string]
Possible Solution
A:
xml: <photoUrl></photoUrl> string]
B:xml: <photoUrl> (wrapped) string]
Context
I noticed the word "OrderedMap" and realized this is a dump of the underlying immutablejs object. Its a fragile solution, affected by changes to the underlying object as well as how future versions of ImmutableJs convert to a string. If not very performant.