nova-specs/506e904394ef20ad7729a38c936...

97 lines
3.9 KiB
Plaintext

{
"comments": [
{
"unresolved": false,
"key": {
"uuid": "d5480c77_910c887f",
"filename": "/PATCHSET_LEVEL",
"patchSetId": 2
},
"lineNbr": 0,
"author": {
"id": 27900
},
"writtenOn": "2024-02-22T12:41:26Z",
"side": 1,
"message": "+1 from me\n\nThere is a bunch of schemas that I created manually for the things missing in the source code. It would be great if we could not only add schemas, but directly fill them and operations with usable descriptions that flow into the spec. With the new sphinx-extension this would completely obsolete the api-ref, otherwise spec generator reads rendered html to extract descriptions from there (but this is not great). Keeping that human activity is unnecessary and error prone as we all know.",
"revId": "506e904394ef20ad7729a38c9366aa5406d68568",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": false,
"key": {
"uuid": "e08fc758_3a1ca21b",
"filename": "/PATCHSET_LEVEL",
"patchSetId": 2
},
"lineNbr": 0,
"author": {
"id": 15334
},
"writtenOn": "2024-02-29T14:44:04Z",
"side": 1,
"message": "I agree. We currently have no `title` or `description` fields. We should add those are part of this effort. I would like us to get to the point where there would be zero human input needed to generate a spec.",
"parentUuid": "d5480c77_910c887f",
"revId": "506e904394ef20ad7729a38c9366aa5406d68568",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "61c12355_2001447c",
"filename": "specs/2024.2/approved/openapi.rst",
"patchSetId": 2
},
"lineNbr": 79,
"author": {
"id": 27900
},
"writtenOn": "2024-02-29T09:48:16Z",
"side": 1,
"message": "I think more reasonable would be to start with schemas already defined in openstack-codegenerator project since they are already mostly reviewed by human for sanity and address document bugs, microversions and actions. This can save quote lot of time.\n\nImportant: openstack-codegenerator does not currently have schemas for deprecated methods",
"revId": "506e904394ef20ad7729a38c9366aa5406d68568",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "6dea2f3c_9a8a94b2",
"filename": "specs/2024.2/approved/openapi.rst",
"patchSetId": 2
},
"lineNbr": 79,
"author": {
"id": 15334
},
"writtenOn": "2024-02-29T14:44:04Z",
"side": 1,
"message": "\u003e I think more reasonable would be to start with schemas already defined in openstack-codegenerator project since they are already mostly reviewed by human for sanity and address document bugs, microversions and actions. This can save quote lot of time.\n\nNot a bad idea.\n\n\u003e Important: openstack-codegenerator does not currently have schemas for deprecated methods\n\nOkay. We don\u0027t want to add these for removed (`HTTP 410 (Gone)`) APIs. We should have them for deprecated APIs though.",
"parentUuid": "61c12355_2001447c",
"revId": "506e904394ef20ad7729a38c9366aa5406d68568",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
},
{
"unresolved": true,
"key": {
"uuid": "7c595494_871316b8",
"filename": "specs/2024.2/approved/openapi.rst",
"patchSetId": 2
},
"lineNbr": 181,
"author": {
"id": 15334
},
"writtenOn": "2024-03-26T17:58:37Z",
"side": 1,
"message": "required",
"range": {
"startLine": 181,
"startChar": 56,
"endLine": 181,
"endChar": 66
},
"revId": "506e904394ef20ad7729a38c9366aa5406d68568",
"serverId": "4a232e18-c5a9-48ee-94c0-e04e7cca6543"
}
]
}