Swagger UI adds continuation characters into the curl example for /api/v1/jobs/flow-scheduling

[tisnik]

You can see it in local instance:
http://localhost:34000//api/v1/ui/#!/Add_new_jobs/f8a_jobs_api_v1_post_flow_scheduling

{code}
curl -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' -d '{ \
"flow_arguments": [ \
{ \
"ecosystem": "npm", \
"force": true, \
"force_graph_sync": false, \
"name": "serve-static", \
"recursive_limit": 0, \
"version": "1.7.1" \
}, \
{ \
"ecosystem": "maven", \
"force": true, \
"force_graph_sync": false, \
"name": "net.iharder:base64", \
"recursive_limit": 1, \
"version": "2.3.9" \
} \
], \
"flow_name": "bayesianFlow" \
}' 'http://localhost:34000/api/v1/jobs/flow-scheduling?job_id=pokus&state=paused'
{code}

That \ characters should not be used because the JSON string is enclosed in apostrophes ie. there are preserved in the data POSTed to the service. This might be Swagger UI issue, we'll need to investigate if new version is fixed....

[fridex]

Currently, we use connexion==1.1.5 which has swagger-ui vendored (see https://github.com/zalando/connexion/tree/master/connexion/vendor) Updating to the newest version (connexion==1.1.10 as of today) did not fix this issue. Worth to report this upstream.