From 456b2fdfe6846fff231a672db4e4964f9a1ce5f5 Mon Sep 17 00:00:00 2001
From: nickcorby <nick.corby24@gmail.com>
Date: Thu, 23 Oct 2025 19:49:26 +1100
Subject: [PATCH 1/2] Create redocly.yaml

---
 .../operation-operationId-exclude-OPTIONS/redocly.yaml | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 configurable-rules/operation-operationId-exclude-OPTIONS/redocly.yaml

diff --git a/configurable-rules/operation-operationId-exclude-OPTIONS/redocly.yaml b/configurable-rules/operation-operationId-exclude-OPTIONS/redocly.yaml
new file mode 100644
index 0000000..d22b0ab
--- /dev/null
+++ b/configurable-rules/operation-operationId-exclude-OPTIONS/redocly.yaml
@@ -0,0 +1,10 @@
+rule/operation-operationId-exclude-OPTIONS:
+  subject:
+    type: Operation
+    filterOutParentKeys:
+      - options
+  assertions:
+    required:
+      - operationId
+  message: Operation is missing 'operationId' property.
+  severity: error

From b71b489fa00488e446a26197820f12e9ab248dc5 Mon Sep 17 00:00:00 2001
From: nickcorby <nick.corby24@gmail.com>
Date: Thu, 23 Oct 2025 19:55:24 +1100
Subject: [PATCH 2/2] Create README.md

---
 .../README.md                                 | 154 ++++++++++++++++++
 1 file changed, 154 insertions(+)
 create mode 100644 configurable-rules/operation-operationId-exclude-OPTIONS/README.md

diff --git a/configurable-rules/operation-operationId-exclude-OPTIONS/README.md b/configurable-rules/operation-operationId-exclude-OPTIONS/README.md
new file mode 100644
index 0000000..d275c45
--- /dev/null
+++ b/configurable-rules/operation-operationId-exclude-OPTIONS/README.md
@@ -0,0 +1,154 @@
+# Variant of the `operation-operationId` rule that excludes `OPTIONS` operations
+
+Author:
+- [@nickcorby](https://github.com/nickcorby)
+
+## What this does and why
+
+This rule extends the built-in rule [operation-operationId](https://redocly.com/docs/cli/rules/oas/operation-operationId) by filtering out set operations e.g. `OPTIONS`.
+
+This rule can be tweaked to exclude any combination of operations, or inversely to **include** set operations. 
+
+## Code
+
+> If you are using a ruleset that includes the `operation-operationId` rule (like `recommended`), you will need to disable this rule in order for the configurable rule to apply.
+> 
+> e.g. if your `redocly.yaml` file contains:
+>
+> ```yaml
+> extends:
+>   - recommended
+> ```
+> You will need to include the following snippet in the `rules` property:
+>
+> ```yaml
+>   rules:
+>     operation-operationId: off
+> ```
+
+This rule is added to your `redocly.yaml` file:
+
+```yaml
+rule/operation-operationId-exclude-OPTIONS:
+  subject:
+    type: Operation
+    filterOutParentKeys:
+      - options
+  assertions:
+    required:
+      - operationId
+  message: Operation is missing 'operationId' property.
+  severity: error
+```
+
+The `filterOutParentKeys` property allows you to define which operations you would like to exclude from the rule:
+
+```yaml
+    type: Operation
+    filterOutParentKeys:
+      - options
+```
+
+This can be extended to multiple operations:
+
+```yaml
+    type: Operation
+    filterOutParentKeys:
+      - options
+      - delete
+```
+
+Alternatively, you can use the `filterInParentKeys` property to define which operations you would like to include in the rule:
+
+```yaml
+    type: Operation
+    filterInParentKeys:
+      - get
+      - post
+```
+
+## Examples
+
+With the rule configured with `severity: error`, the following snippet of a `GET` operation will trigger this rule & display an error:
+
+```yaml
+get:
+  tags:
+  - Endpoint
+  summary: "Example endpoint."
+  parameters:
+  - name: "Authorization"
+    in: "header"
+    description: "Auth Token"
+    required: true
+    schema:
+      type: "string"
+  responses:
+    "200":
+      description: "200 response"
+      headers:
+        Access-Control-Allow-Origin:
+          schema:
+            type: "string"
+      content:
+        application/json:
+          schema:
+            $ref: ../models/200Response.yaml
+    "400":
+      description: "400 response"
+      headers:
+        Access-Control-Allow-Origin:
+          schema:
+            type: "string"
+      content:
+        application/json:
+          schema:
+            $ref: ../models/ErrorResponse.yaml
+  security:
+  - Authorizer: []
+  - api_key: []
+```
+
+However, the following snippet of an `OPTIONS` operation **won't** trigger the rule:
+
+```yaml
+options:
+  tags:
+  - Endpoint
+  summary: "Example endpoint."
+  parameters:
+  - name: "Authorization"
+    in: "header"
+    description: "Auth Token"
+    required: true
+    schema:
+      type: "string"
+  responses:
+    "200":
+      description: "200 response"
+      headers:
+        Access-Control-Allow-Origin:
+          schema:
+            type: "string"
+      content:
+        application/json:
+          schema:
+            $ref: ../models/200Response.yaml
+    "400":
+      description: "400 response"
+      headers:
+        Access-Control-Allow-Origin:
+          schema:
+            type: "string"
+      content:
+        application/json:
+          schema:
+            $ref: ../models/ErrorResponse.yaml
+  security:
+  - Authorizer: []
+  - api_key: []
+```
+
+## References
+
+Assisted by [AlbinaBlazhko17](https://github.com/AlbinaBlazhko17)