api-naming-conventions

Use underscores instead of hyphens in all URL path segments and path variables, such as /companies/{comp_id}/equipment_usage/{id}. Audit the OpenAPI spec with grep for hyphenated path segments and update @PathVariable names in controllers to match.

OperationId values should use lowerCamelCase, such as getEquipmentUsageById or crupdateEquipmentUsages. This follows the OpenAPI Generator convention so generated Java and TypeScript client methods have idiomatic names.

Query parameters should use snake_case, for example @RequestParam(name = "page_size"). The Java variable can remain camelCase while the external parameter name stays snake_case via the name attribute.

Run grep for hyphenated path segments, such as searching for '-{' in api.yml, to find non-compliant paths. Then manually verify that all @PathVariable and @RequestParam names in controllers use snake_case and operationIds use camelCase.

Hyphens are only acceptable where external standards require kebab-case, such as certain file names. Within the project's REST paths, query parameters, and schema properties, underscores are mandatory with no exceptions.