Skip to content

Conversation

@hanspagel
Copy link

@hanspagel hanspagel commented Jul 28, 2025

Hey @RobinTail! Just discovered your awesome project and thought it would be cool to add an example how you can easily generate a Scalar API Reference for the generated OpenAPI document.

I wondered if I could add it where the Swagger UI example is, but the section is actually about the middleware, so I thought a new section could be better.

What do you think? Helpful? Excited to hear your thoughts!

Summary by CodeRabbit

  • Documentation
    • Added a new section explaining how to serve OpenAPI documentation using Scalar, including installation steps and integration instructions for Express apps.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 28, 2025

Walkthrough

A new section has been added to the README under "Integration and Documentation," detailing how to serve OpenAPI documentation using Scalar. The section includes installation instructions for the Scalar package and an example of integrating its middleware into an Express app. No code or API changes were made.

Changes

Cohort / File(s) Change Summary
README Update
README.md
Added a "Serving documentation with Scalar" section, including installation and integration example.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

In README fields where docs now grow,
A Scalar breeze begins to blow.
With npm install and middleware delight,
OpenAPI shines so bright.
Rabbits leap through docs anew—
Express and Scalar, serving you!
🐇📄✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests 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
Contributor

@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: 0

🧹 Nitpick comments (1)
README.md (1)

1142-1170: Clarify where documentation is coming from in the example snippet

The snippet assumes the existence of a documentation instance that exposes getSpecAsJson(), but the README never establishes that variable. Readers who copy-paste will hit a “documentation is not defined” error.

Consider briefly showing (or linking to) the earlier “Creating a documentation” section and assigning the variable explicitly:

-import { createConfig } from "express-zod-api";
+import { createConfig, Documentation } from "express-zod-api"; // <-- bring Documentation in

 // somewhere above …
-const config = createConfig({
+const documentation = new Documentation({ routing, config }).getSpecAsJson();

+const config = createConfig({
   beforeRouting: ({ app, getLogger }) => {
     …
     app.use(
       "/docs",
       apiReference({
-        // Pass your generated OpenAPI document
-        content: documentation.getSpecAsJson(),
+        content: documentation, // clearly defined variable
       }),
     );
   },
 });

A one-line note (“Assuming you created a documentation object as shown in the previous section”) would be enough if you prefer not to duplicate code.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e875b3c and 95e0e0e.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: RobinTail
PR: RobinTail/express-zod-api#2546
File: example/factories.ts:35-42
Timestamp: 2025-05-27T20:03:34.213Z
Learning: The `./example` directory in the express-zod-api repository contains demonstration code for educational purposes only, not intended for production use. Example code can make simplified assumptions for brevity and clarity, and should not be flagged for missing production-level error handling, security measures, or edge case handling.
README.md (1)

Learnt from: RobinTail
PR: #2546
File: example/factories.ts:35-42
Timestamp: 2025-05-27T20:03:34.213Z
Learning: The ./example directory in the express-zod-api repository contains demonstration code for educational purposes only, not intended for production use. Example code can make simplified assumptions for brevity and clarity, and should not be flagged for missing production-level error handling, security measures, or edge case handling.

@RobinTail
Copy link
Owner

image

I wish you all the best with your project, but won't allow to abuse my Readme for promotion purposes.

@RobinTail RobinTail closed this Jul 28, 2025
@hanspagel
Copy link
Author

Oh, I’m so sorry. I just thought it might be helpful for the users of express-zod-api.

I added the example to our docs [1][2], that should work, too. ✌️

[1] scalar/scalar#6398
[2] https://guides.scalar.com/scalar/scalar-api-references/integrations/express#usage-with-express-zod-api

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants