)]}'
{"api-ref/source/parameters.yaml":[{"author":{"_account_id":31737,"name":"Hirotaka Wakabayashi","email":"hiwkby@yahoo.com","username":"hiwkby"},"change_message_id":"defe6aec9dcf5a54aeef45cd28914c288bfed32c","unresolved":true,"context_lines":[{"line_number":1001,"context_line":"    most databases will crash or become readonly."},{"line_number":1002,"context_line":"  in: body"},{"line_number":1003,"context_line":"  required: false"},{"line_number":1004,"context_line":"  type: string"},{"line_number":1005,"context_line":"wal_archive_size:"},{"line_number":1006,"context_line":"  description: |"},{"line_number":1007,"context_line":"    The used space of the WAL archive folder, in bytes."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"cded3eec_217a06a6","line":1004,"updated":"2026-03-17 19:58:45.000000000","message":"Hi Erkin, thanks for the patch.\n\nI noticed the API response formats the percentage value as a string \n(e.g., \"13.33%\") in the view layer. This makes it harder for clients to \nvalidate or perform numeric operations on the field.\n\nWould you consider this alternative approach:\n1. Return the percentage as **numeric only** in the API response (e.g., 13.33)\n2. Document the unit (%) in the **API documentation**\n3. Let the **UI layer** handle formatting (adding the % symbol)\n\nThis keeps the client-side logic simpler and makes the data more reusable for \napplications that may need numeric calculations. What do you think?","commit_id":"35dceef2b6b3d1f3edea6131cdc254b5518b9c0c"},{"author":{"_account_id":36080,"name":"Erkin Mussurmankulov","display_name":"Eric","email":"mangust404@gmail.com","username":"mongoose404","status":"PS Cloud services employee"},"change_message_id":"c6fb9219f0572c01ab9c54a90de78f8222d8ac0e","unresolved":false,"context_lines":[{"line_number":1001,"context_line":"    most databases will crash or become readonly."},{"line_number":1002,"context_line":"  in: body"},{"line_number":1003,"context_line":"  required: false"},{"line_number":1004,"context_line":"  type: string"},{"line_number":1005,"context_line":"wal_archive_size:"},{"line_number":1006,"context_line":"  description: |"},{"line_number":1007,"context_line":"    The used space of the WAL archive folder, in bytes."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"ed86c1e1_3b132a01","line":1004,"in_reply_to":"cded3eec_217a06a6","updated":"2026-03-18 15:45:46.000000000","message":"Sure, that\u0027s a good point. I\u0027ve also made corresponding changes for [python-troveclient](https://review.opendev.org/c/openstack/python-troveclient/+/973106)","commit_id":"35dceef2b6b3d1f3edea6131cdc254b5518b9c0c"}]}