docs: re-word the rule explanation, add link to operationId blog post

Redocly · Dec 1, 2023 · 973b067 · 973b067
1 parent b951bf5
commit 973b067
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/docs/rules/operation-operationId.md b/docs/rules/operation-operationId.md
@@ -15,11 +15,10 @@ Requires each operation to have an `operationId` defined.
 ## API design principles
 
 The `operationId` is used by tooling to identify operations (which are otherwise done through scary looking JSON pointers).
+OpenAPI does not consider `operationId` a required field, but we'd describe it as a strongly recommended field.
 
 This rule is unopinionated.
 
-If it annoys the lazy or minimalists, offer them an alternative: two weeks at Redocly Bootcamp.
-
 ## Configuration
 
 | Option   | Type   | Description                                                                               |
@@ -72,6 +71,7 @@ paths:
 
 ## Resources
 
+- [OperationIds make good API design - Redocly Blog](https://redocly.com/blog/operationid-is-api-design/)
 - [Rule source](https://github.com/Redocly/redocly-cli/blob/main/packages/core/src/rules/common/operation-operationId.ts)
 - [Operation object docs](https://redocly.com/docs/openapi-visual-reference/operation/)
 - Consider using [configurable rules](./configurable-rules.md) for more specific rules for `operationId`s such as length, casing, and pattern enforcement.