Fixed syntax errors in api-with-examples.yaml

[mabar]

With original, php implementation of yaml symfony/yaml I got some syntax errors. This PR fixes them.

Online parsers which consider current file valid:

• https://www.json2yaml.com
• http://www.yamllint.com
• https://yaml-online-parser.appspot.com

Online parsers which reports error:

• https://codebeautify.org/yaml-validator
• https://jsonformatter.org/yaml-validator
• https://onlineyamltools.com/validate-yaml
• https://onlineyamltools.com/edit-yaml

With proposed changes is file valid for all of them

[cebe]

Seems inline YAML spanning multiple lines was not officially supported in symfony/yaml until version 4.4: symfony/symfony#34805 (comment) (there is also a bug with parsing these in the current version, which is reported in the linked issue)

[mabar]

Tried latest version of files with symfony/yaml 4.4 and 5.0 and api-with-examples.yaml now work. But upsto.yaml stopped working. Symfony bug, I guess, I don't see any problems in current syntax

 Symfony\Component\Yaml\Exception\ParseException: Malformed inline YAML string: {
"total": 2,
"apis": [
{
"apiKey": "oa_citations",
"apiVersionNumber": "v1",
"apiUrl": "https://developer.uspto.gov/ds-api/oa_citations/v1/fields",
"apiDocumentationUrl": "https://developer.uspto.gov/ds-api-docs/index.html?url=https://developer.uspto.gov/ds-api/swagger/docs/oa_citations.json"
},
{
"apiKey": "cancer_moonshot",
"apiVersionNumber": "v1",
"apiUrl": "https://developer.uspto.gov/ds-api/cancer_moonshot/v1/fields",
"apiDocumentationUrl": "https://developer.uspto.gov/ds-api-docs/index.html?url=https://developer.uspto.gov/ds-api/swagger/docs/cancer_moonshot.json"
}
]
} at line 64 (near "}").
in symfony/yaml/Inline.php(300)
in symfony/yaml/Inline.php(375) Symfony\Component\Yaml\Inline::parseScalar()
in symfony/yaml/Inline.php(473) Symfony\Component\Yaml\Inline::parseSequence()
in symfony/yaml/Inline.php(85) Symfony\Component\Yaml\Inline::parseMapping()
in symfony/yaml/Parser.php(366) Symfony\Component\Yaml\Inline::parse()
in symfony/yaml/Parser.php(516) Symfony\Component\Yaml\Parser->doParse()
in symfony/yaml/Parser.php(312) Symfony\Component\Yaml\Parser->parseBlock()
in symfony/yaml/Parser.php(516) Symfony\Component\Yaml\Parser->doParse()
in symfony/yaml/Parser.php(312) Symfony\Component\Yaml\Parser->parseBlock()
in symfony/yaml/Parser.php(516) Symfony\Component\Yaml\Parser->doParse()
in symfony/yaml/Parser.php(312) Symfony\Component\Yaml\Parser->parseBlock()
in symfony/yaml/Parser.php(516) Symfony\Component\Yaml\Parser->doParse()
in symfony/yaml/Parser.php(312) Symfony\Component\Yaml\Parser->parseBlock()
in symfony/yaml/Parser.php(516) Symfony\Component\Yaml\Parser->doParse()
in symfony/yaml/Parser.php(312) Symfony\Component\Yaml\Parser->parseBlock()
in symfony/yaml/Parser.php(516) Symfony\Component\Yaml\Parser->doParse()
in symfony/yaml/Parser.php(312) Symfony\Component\Yaml\Parser->parseBlock()
in symfony/yaml/Parser.php(516) Symfony\Component\Yaml\Parser->doParse()
in symfony/yaml/Parser.php(312) Symfony\Component\Yaml\Parser->parseBlock()
in symfony/yaml/Parser.php(516) Symfony\Component\Yaml\Parser->doParse()
in symfony/yaml/Parser.php(312) Symfony\Component\Yaml\Parser->parseBlock()
in symfony/yaml/Parser.php(95) Symfony\Component\Yaml\Parser->doParse()
in symfony/yaml/Parser.php(63) Symfony\Component\Yaml\Parser->parse()
in symfony/yaml/Yaml.php(57) Symfony\Component\Yaml\Parser->parseFile()
in cases/Schema/ExamplesTest.phpt(65) Symfony\Component\Yaml\Yaml::parseFile()

[MikeRalphson]

@cebe@mabar Can we not use a YAML library which supports the whole of the 1.2 spec and uses the official YAML test suite? If that means ditching PHP from the proposed GitHub actions, then so be it, and here's a vote to use Javascript instead as per the existing (and a couple of proposed) Travis CI jobs.

[cebe]

Can we not use a YAML library which supports the whole of the 1.2 spec and uses the official YAML test suite? If that means ditching PHP from the proposed GitHub actions, then so be it.

As far as I see there is no PHP library that matches the criteria. Most stable and supported library is the one we are using right now.

However the version I am using in the github action works well with our current set of example YAML files. The issue shown above in upsto.yaml is a bug that exists in symfony >=4.4.

I suggest to keep the current implementation now (as it is working) and replace it with a javascript implementation when someone has time to work on that.

[darrelmiller]

Closing as this is a duplicate of #1914