Skip to content
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

Improve scalar docs: document 'cdn' setting #3006

Merged
merged 3 commits into from
Mar 11, 2025

Conversation

IvaDey
Copy link
Contributor

@IvaDey IvaDey commented Mar 11, 2025

Information

Type Breaking change
Fix No
Doc No

Document cdn setting of scalar and remove _integration from settings because the "tsed" value is not supported by the latest version of @scalar/api-reference.

Summary by CodeRabbit

  • Refactor
    • Streamlined configuration settings by removing an obsolete integration detail for a cleaner structure.
  • Documentation
    • Corrected the formatting of "Ts.ED" in the Scalar documentation for consistency.
    • Improved clarity in the documentation table header with formatting adjustments.

Copy link

coderabbitai bot commented Mar 11, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

The update removes the _integration property from the settings object in the ScalarModule and from the opts object in the indexMiddleware function. Additionally, a minor correction was made in the documentation to ensure consistent formatting of "TsED."

Changes

File(s) Change Summary
packages/specs/scalar/.../ScalarModule.ts
packages/specs/scalar/.../indexMiddleware.ts
Removed the _integration property (previously set to "tsed") from the returned objects/options. Other properties remain unchanged.
docs/.../scalar.md Corrected the formatting of "TsED" from "Ts.ED" to ensure consistency.

Possibly related PRs


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 06e445c and d6bc786.

📒 Files selected for processing (2)
  • docs/tutorials/scalar.md (2 hunks)
  • docs/tutorials/scalar.md (3 hunks)

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a 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: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d0cd0f2 and d704b2b.

📒 Files selected for processing (3)
  • packages/specs/scalar/src/ScalarModule.ts (0 hunks)
  • packages/specs/scalar/src/middlewares/indexMiddleware.ts (0 hunks)
  • docs/tutorials/scalar.md (2 hunks)
💤 Files with no reviewable changes (2)
  • packages/specs/scalar/src/middlewares/indexMiddleware.ts
  • packages/specs/scalar/src/ScalarModule.ts
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/tutorials/scalar.md

96-96: Fenced code blocks should be surrounded by blank lines
null

(MD031, blanks-around-fences)


112-112: Fenced code blocks should be surrounded by blank lines
null

(MD031, blanks-around-fences)

⏰ Context from checks skipped due to timeout of 90000ms (9)
  • GitHub Check: test-third-parties (20.12.2)
  • GitHub Check: test-specs (20.12.2)
  • GitHub Check: test-security (20.12.2)
  • GitHub Check: test-platform (20.12.2)
  • GitHub Check: test-graphql (20.12.2)
  • GitHub Check: test-orm (20.12.2)
  • GitHub Check: test-core (20.12.2)
  • GitHub Check: lint (20.12.2)
  • GitHub Check: CodeQL-Build

Copy link

@coderabbitai coderabbitai bot left a 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: ASSERTIVE
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d704b2b and 06e445c.

📒 Files selected for processing (2)
  • docs/tutorials/scalar.md (2 hunks)
  • docs/tutorials/scalar.md (1 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/tutorials/scalar.md

96-96: Fenced code blocks should be surrounded by blank lines
null

(MD031, blanks-around-fences)


112-112: Fenced code blocks should be surrounded by blank lines
null

(MD031, blanks-around-fences)

⏰ Context from checks skipped due to timeout of 90000ms (9)
  • GitHub Check: test-third-parties (20.12.2)
  • GitHub Check: test-specs (20.12.2)
  • GitHub Check: test-security (20.12.2)
  • GitHub Check: test-platform (20.12.2)
  • GitHub Check: test-orm (20.12.2)
  • GitHub Check: lint (20.12.2)
  • GitHub Check: test-graphql (20.12.2)
  • GitHub Check: test-core (20.12.2)
  • GitHub Check: CodeQL-Build
🔇 Additional comments (2)
docs/tutorials/scalar.md (2)

75-80: Capitalize "URL" in the cdn Option Description

In the options table, the new cdn row currently describes the URL as “Url to the @scalar/api-reference package.” To improve clarity and consistency with common usage, please change “Url” to “URL.”

-| cdn                  | `https://cdn.jsdelivr.net/npm/@scalar/api-reference`          | Url to the @scalar/api-reference package.                                                             |
+| cdn                  | `https://cdn.jsdelivr.net/npm/@scalar/api-reference`          | URL to the @scalar/api-reference package.                                                             |
🧰 Tools
🪛 LanguageTool

[uncategorized] ~79-~79: Did you mean: “By default,”?
Context: ... | OpenAPI file name. By default openapi.json. ...

(BY_DEFAULT_COMMA)


1-180: Overall Documentation Update Approved

The updated documentation successfully introduces the new cdn configuration option and removes the deprecated _integration setting as intended. The structure is clear and the examples are well integrated into the existing content.

🧰 Tools
🪛 LanguageTool

[uncategorized] ~27-~27: The preposition “to” seems more likely in this position.
Context: ...` Then add the following configuration in your Server: <<< @/tutorials/snippets/...

(AI_EN_LECTOR_REPLACEMENT_PREPOSITION)


[uncategorized] ~79-~79: Did you mean: “By default,”?
Context: ... | OpenAPI file name. By default openapi.json. ...

(BY_DEFAULT_COMMA)

🪛 markdownlint-cli2 (0.17.2)

13-13: Inline HTML
Element: Banner

(MD033, no-inline-html)


88-88: Bare URL used
null

(MD034, no-bare-urls)


96-96: Fenced code blocks should be surrounded by blank lines
null

(MD031, blanks-around-fences)


112-112: Fenced code blocks should be surrounded by blank lines
null

(MD031, blanks-around-fences)


175-175: Inline HTML
Element: GithubContributors

(MD033, no-inline-html)


179-179: Inline HTML
Element: GithubContributors

(MD033, no-inline-html)

@Romakita Romakita merged commit e9efef0 into tsedio:production Mar 11, 2025
1 of 9 checks passed
@Romakita
Copy link
Collaborator

🎉 This PR is included in version 8.5.4 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants