Fix lint issue

[DagonWat]

Motivation

Broken CI was blocking us a bit on fixing Gitbook

Changes

• Ignore the error incorrectly raised by linter, it was a bug in linter - Missing null guard causes "Cannot read properties of null (reading 'enum')"  stoplightio/spectral#2959

[coderabbitai]

📝 Walkthrough

Walkthrough

The .spectral.yaml configuration file is updated to disable the duplicated-entry-in-enum OpenAPI linting rule, preventing that Spectral validation check from executing during lint runs.

Changes

Spectral Validation Configuration

Layer / File(s)	Summary
Disable duplicated-entry-in-enum rule .spectral.yaml	Spectral rule configuration is extended to disable the duplicated-entry-in-enum OpenAPI validation rule.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• mailtrap/mailtrap-openapi#2: Both PRs modify Spectral configuration in .spectral.yaml to disable specific OpenAPI lint rules during Spectral runs.

Suggested reviewers

• IgorDobryn
• mklocek
• VladimirTaytor

Poem

🐰 A single line, so small and neat,
One rule disabled—the config's complete!
No more enum duplicates to bemoan,
Spectral checks pass with a satisfied groan! ✨

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description partially follows the template but is incomplete. It includes Motivation and Changes sections but omits the required 'How to test' section with test checkboxes and the 'Images and GIFs' comparison table.	Add the missing 'How to test' section with at least one test step as a checkbox, and include the 'Images and GIFs' table with before/after comparisons if applicable to this change.
Title check	❓ Inconclusive	The title 'Fix lint issue' is vague and generic, using non-descriptive terms that don't convey the specific change made to the codebase.	Consider a more descriptive title such as 'Disable duplicated-entry-in-enum rule in Spectral configuration' that clearly identifies what was changed and why.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-lint-issues

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

🧹 Nitpick comments (1)

.spectral.yaml (1)

7-7: ⚡ Quick win

Add explanatory comment for consistency and maintainability.

Line 6's rule disablement includes a clear comment explaining the rationale. Line 7 should follow the same pattern to help future maintainers understand why this rule is disabled.

📝 Suggested improvement

  oas3-valid-media-example: off
+ # TODO: Document why duplicated-entry-in-enum is disabled
  duplicated-entry-in-enum: off

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.spectral.yaml at line 7, Add a short explanatory comment next to the
duplicated-entry-in-enum: off setting so maintainers know why this rule is
disabled; update the .spectral.yaml entry for duplicated-entry-in-enum to mirror
the style used for the prior rule (line 6) by adding a one-line comment
describing the rationale and any relevant context or exceptions.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In @.spectral.yaml:
- Line 7: Add a short explanatory comment next to the duplicated-entry-in-enum:
off setting so maintainers know why this rule is disabled; update the
.spectral.yaml entry for duplicated-entry-in-enum to mirror the style used for
the prior rule (line 6) by adding a one-line comment describing the rationale
and any relevant context or exceptions.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: cb5d30c9-069c-45ff-89b5-383d5cce44b6

📥 Commits

Reviewing files that changed from the base of the PR and between b4a29cb and 9363652.

📒 Files selected for processing (1)

• .spectral.yaml