Closed florian-baltes-nextview closed 3 months ago
MuleSoft validates the OTM5 swagger.json file after I performed the following operations on it:
"Bearer token"
with "bearer_token"
over the whole document (basically renaming the Bearer token security scheme to match the regex in the error)Hello @florian-baltes-nextview, thanks for your contribution. I do have a few follow up questions:
Hello @bmeesters. Thank you for picking this up so fast:
For line 9894, the json (downloaded today from https://otm5.opentripmodel.org/) looks like this to me:
You can see that the "eventType",
line is duplicate. This is causing the validation to fail. Same applies to line 13727:
Thanks, I downloaded the file from this repository, but it seems those are not in sync. I'll see if I can get rid of the duplicate lines. Note that the swagger is generated, so it is not that easy to just remove them since then we have to check it every time we make a change again. Any way, this is worth fixing, cannot promise yet when though.
Thank you @bmeesters. there is no time criticality for me here as I fixed those lines myself. I just thought its worth mentioning :)
Alright good to know! And thanks for bringing it up, always nice if people help getting OTM5 better! I'll keep the issue open until it is actually fixed so you get a notification whenever that happens.
Since Mulesoft is closed software we will close this issue. We will take into account the feedback we got regarding duplicate discriminators and separate strings for the next version though to avoid the problems where possible.
Type of bug
Describe the bug The current OTM5-Specification can not be imported into MuleSoft as it fails the built in validation in three different places:
9894
13727
26670
^[a-zA-Z0-9\.\-_]+$
for component declarationsTo Reproduce Steps to reproduce the behavior:
Expected behavior Validation for OTM5 swagger.json file should pass
Screenshots n/a
Technical information (only if the bug is a fault in the rendering) n/a
Additional context n/a