-
Notifications
You must be signed in to change notification settings - Fork 32
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
DEVDOCS-4878: [external] API specs, update Operation IDs to be consis…
…tent & programmatic (#45) <!-- Ticket number or summary of work --> # [DEVDOCS-4878] > As per OpenAPI specification guidance for operationID field, follow programmatic conventions for operationId field. To me that means as if I were defining a method or function name. > This field is not used in the API docs as far as I can tell. There were many different naming conventions across APIs. I've aligned to be camel case. > This helps facilitate API SDK generation as all endpoints can have a function name based on the operation ID and have it have sufficient context to be unique amongst all APIs. ## What changed? * Make operation IDs consistent and follow programmatic conventions ## Release notes draft * A valued partner has put in the heroic work to make the OAS operation IDs programmatic across our public APIs. The operationId property is now consistently camelCase and relates to the plain-language name of the endpoint. Thanks, @bobbyshaw! ## Anything else? * Original PR [bigcommerce/api-specs 1469](bigcommerce/api-specs#1469) * Related Issue [bigcommerce/api-specs 1143](bigcommerce/api-specs#1143) * Tag for last commit before this -- https://github.com/bigcommerce/docs/releases/tag/before-operation-id-change --------- Co-authored-by: Tom Robertshaw <[email protected]>
- Loading branch information
Showing
52 changed files
with
478 additions
and
458 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.