fix: use string values when generating conformanceStatus enum doc

I just made a mvn clean package on master and for me the values are already fine in the generated doc:

Values: approved, empty, not_reviewed, rejected

Not sure if there is really anything to change ?

Okay, sorry, I didn't get it at first as I thought they were the correct values accepted by the endpoint.

So I've built your branch to see what it gives, and I think this is not perfect neither:

Values: approved, `, `not reviewed, rejected

Not sure where you are checking that specifically. I have checked the aou-api.json and the values are correct: "odConformance" : { "description" : "The OD conformance status", "enum" : [ "approved", "", "not reviewed", "rejected" ], "type" : "string" }, "osdConformance" : { "description" : "The OSD conformance status", "enum" : [ "approved", "", "not reviewed", "rejected" ], "type" : "string" },

Then in the portail, it's interpreted as:

The value I wrote is what we get in AoU-APIs.html and AoU-APIs.pdf. The empty string is probably not supported correctly when generating these files.

added 7 commits

• ba6765dd...f68df599 - 6 commits from branch master
• 2b87328b - fix: use string values when generating conformanceStatus enum doc

Compare with previous version

merged