Skip to content

feat: include provider type in schema#34

Merged
jiashengguo merged 1 commit into
devfrom
jiasheng
Apr 16, 2026
Merged

feat: include provider type in schema#34
jiashengguo merged 1 commit into
devfrom
jiasheng

Conversation

@jiashengguo
Copy link
Copy Markdown
Member

@jiashengguo jiashengguo commented Apr 16, 2026

Summary by CodeRabbit

  • New Features

    • API schema endpoint now includes provider information in the response.
  • Chores

    • Package version updated to 0.4.2.

Copilot AI review requested due to automatic review settings April 16, 2026 03:42
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 16, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: fa4ffc29-b5b4-44be-9627-8f1e8e365ff4

📥 Commits

Reviewing files that changed from the base of the PR and between 81099de and ab6f5a8.

📒 Files selected for processing (2)
  • package.json
  • src/server.ts

📝 Walkthrough

Walkthrough

The pull request bumps the package version from 0.4.1 to 0.4.2 and enhances the /api/schema endpoint to include provider information sourced from the datasource configuration in the response payload.

Changes

Cohort / File(s) Summary
Version Bump
package.json
Updated package version from 0.4.1 to 0.4.2.
Endpoint Enhancement
src/server.ts
Added provider field to /api/schema endpoint response containing the datasource provider type from zmodelConfig.datasource.provider.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A patch release hops into place,
With version bumped—0.4.2's the trace!
The schema endpoint spreads its wing,
Now proudly showing provider's bling ✨
Clean changes, organized and bright—
Our bundle's ready, oh what a sight! 🎉

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'feat: include provider type in schema' directly and accurately describes the main change: adding a provider type field to the /api/schema endpoint response in src/server.ts.
Docstring Coverage ✅ Passed Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✏️ 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 jiasheng

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

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

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds datasource provider information to the schema metadata returned by the proxy server, enabling downstream consumers (e.g., tooling that inspects /api/schema) to detect the backing database provider type.

Changes:

  • Extend GET /api/schema response to include provider.type from zmodelConfig.datasource.provider.
  • Bump package version to 0.4.2.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
src/server.ts Adds provider.type into the /api/schema response payload alongside existing metadata.
package.json Increments package version from 0.4.1 to 0.4.2.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@jiashengguo jiashengguo merged commit 1d0712a into dev Apr 16, 2026
7 checks passed
@jiashengguo jiashengguo deleted the jiasheng branch April 16, 2026 03:44
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