Open jwalgran opened 4 years ago
Two additional users have encountered problems connecting with the API due to this bug:
1) On 5th May 2) On 22nd June
On both occasions their issues were resolved by following the instructions in the additional documentation created by @jwalgran
https://docs.google.com/document/d/1ZKCN84Eu9WDAXUokojOw7Dcg5TAJw0vKnVk7RPrTPZ0/edit?usp=sharing
We're receiving increased levels of interest in our API and therefore more users encountering this issue. Could we include this fix in the next update, if at all possible @jwalgran ?
cc @dboyer
@katieashaw We picked PPE related tasks for this sprint rather than this issue but have added it to our priority backlog to get to if we have time.
Got it, thank you!
Overview
The curl command for POSTing new facilty generated by Swagger UI contains \ characters intended to be interpreted as line continuations but are instead being included in the literal JSON string, resulting in an invalid request.
Removing the \ characters results in a successful request
Expected Behavior
The curl example can be copy-pasted into a terminal and run successfully.
Actual Behavior
The copy-pasted command makes an invalid request.
Steps to Reproduce
Token abc123...
using a valid token value for an account that is a member of thecan_submit_facility
group.data
field, setcreate
tofalse
and submit the request.Additional Context
If it is not possible to easily modify the generated curl we should at least include a bold message at the bottom of the example text, just above the "Try it out" section, that clearly states that the
\
characters need to be removed.