-
-
Notifications
You must be signed in to change notification settings - Fork 31
docs: add description for new plugin option "includeOpenApiIgnored" #486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: add description for new plugin option "includeOpenApiIgnored" #486
Conversation
The latest updates on your projects. Learn more about Vercel for GitHub.
|
WalkthroughAdds a new OpenAPI plugin option Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Tip 🔌 Remote MCP (Model Context Protocol) integration is now available!Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats. ✨ Finishing Touches🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
docs/reference/plugins/openapi.mdx
(2 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/reference/plugins/openapi.mdx
[grammar] ~29-~29: There might be a mistake here.
Context: .... | No | false | | omitInputDetails | Boolean | **Only va...
(QB_NEW_EN)
🔇 Additional comments (1)
docs/reference/plugins/openapi.mdx (1)
183-185
: Clear and helpful explanation of default behavior and dual-spec use caseThe added context around default exclusion and when to set
includeOpenApiIgnored
is concise and useful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
docs/reference/plugins/openapi.mdx (1)
2-2
: Minor wording tweak: align “OpenAPI 3.0” with 3.1 usage elsewhereFront matter says “OpenAPI 3.0” while the default
specVersion
is3.1.0
and the link points to 3.1. Suggest making it version-agnostic.Apply this diff:
-description: Plugin for generating OpenAPI 3.0 specifications +description: Plugin for generating OpenAPI 3.x specifications
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
docs/reference/plugins/openapi.mdx
(2 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/reference/plugins/openapi.mdx
[grammar] ~29-~29: There might be a mistake here.
Context: .... | No | false | | omitInputDetails | Boolean | **Only va...
(QB_NEW_EN)
🔇 Additional comments (2)
docs/reference/plugins/openapi.mdx (2)
29-29
: Option description correctly references@@openapi.ignore
Good fix aligning the option description with the actual attribute syntax.
183-199
: Great clarification and example; distinct plugin block names are spot-onClear explanation of dual-spec generation and using unique block names (
openapiPublic
/openapiInternal
). This avoids collisions and makes the config self-explanatory.
Updating the docs of
@zenstackhq/openapi
following this PR:zenstackhq/zenstack#2221
It describes the usage of the new plugin option "includeOpenApiIgnored".
Summary by CodeRabbit