Numerous fixes to make Swagger parseable and comply with data.

[monty241]

Numerous fixes to make Swagger parseable and comply with actual data with standard swagger parser of Invantive SQL.

[oblakeerickson]

Thank you very much for this. My first issue is that we need to edit the yml file like it says in the readme

To edit the api docs, edit the openapi.yml file not the json file.

and then we can convert it to json from there with the node tojson.js script, so that we only have 1 source of truth.

I think this might be where all the extra newline characters are coming from? So there might be a bug or a setting we need to tweak to remove them.

[oblakeerickson]

After diving in a bit, looks like the extra \n's are from the misuse of the | operator in yaml
https://yaml-multiline.info/

Block Style Indicator: The block style indicates how newlines inside the block should behave. If you would like them to be kept as newlines, use the literal style, indicated by a pipe (|).

[oblakeerickson]

I think we should split this pr into two separate pr's because there are so many \n issues. First make one pr that edits the yaml files and replaces the | character with >- so that when we run tojson.js we not longer have the extra newlines in the json.

Then make another pr with the remaining changes to the yaml files.

I unfortunately cannot accept this pr as is because any future changes we need to make to the yaml files will overwrite the changes you have in the openapi.json file by tojson.js.

[monty241]

Hi,

OK. It is quite hard for us to work with the yaml files. I will withdraw the pull request. We will be testing and combining the PUT/POST API's into SQL insert/update/delete statements, so more issues may arise.