Skip to content

docs: added @piying/orm extension to readme #11596

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.

Sign up for GitHub

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

Jump to bottom
Merged
alumni merged 2 commits into from
Aug 16, 2025
Merged

docs: added @piying/orm extension to readme #11596

alumni merged 2 commits into from
Aug 16, 2025

Conversation

@wszgrcy
Copy link
Contributor

@wszgrcy wszgrcy commented Aug 13, 2025 •
edited by coderabbitai bot
Loading

Description of change

added "piying-orm" extension to readme
Update README.md

Pull-Request Checklist

  • Code is up-to-date with the master branch
  • This pull request links relevant issues as Fixes #00000
  • There are new or updated unit tests validating the change
  • Documentation has been updated to reflect this change

Summary by CodeRabbit

  • Documentation
    • Added a new README Extensions entry: “Generate TypeORM entities from Valibot schemas” with a link to the piying-orm project for easier discovery.
    • Clarifies available ecosystem options for users exploring extensions.
    • No changes to code, API, or runtime behavior.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 13, 2025 •
edited
Loading

Walkthrough

Added a new Extensions entry in README.md linking “Generate TypeORM entities from Valibot schemas” to piying-orm. Documentation-only change; no code, API, or runtime behavior affected.

Changes

Cohort / File(s) Summary of Changes
Documentation
README.md		 Added new Extensions item: “Generate TypeORM entities from Valibot schemas” linking to piying-orm. No code, API, or runtime behavior affected.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nibbled through README leaves tonight,
A tiny link tucked in the light.
No code disturbed, just words to see—
A bridge to piying-orm for Devs like me.
Hop on, hop off, the docs feel right. 🥕🐇

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between d6306c4 and df26c90.

📒 Files selected for processing (1)
  • README.md (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • README.md
✨ 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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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.

coderabbitai[bot]
coderabbitai bot reviewed Aug 13, 2025
View reviewed changes
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)

198-198: Clarify phrasing and fix TypeORM casing for consistency.

The current text is ungrammatical and uses lowercase "typeorm". Suggest rewording to match the style of other bullets and correctly capitalize "TypeORM".

--   Valibot define to typeorm entity - [piying-orm](https://github.com/piying-org/piying-orm)
+-   Generate TypeORM entities from Valibot schemas - [piying-orm](https://github.com/piying-org/piying-orm)
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 6e9f20d and d6306c4.

📒 Files selected for processing (1)
  • README.md (1 hunks)
🔇 Additional comments (1)
README.md (1)

198-198: External link verified

The GitHub repository piying-org/piying-orm is reachable (HTTP 200) and exists at the expected URL. No broken link detected—no further action needed.

@coveralls
Copy link

coveralls commented Aug 13, 2025

Coverage Status

coverage: 76.353%. remained the same
when pulling df26c90 on piying-org:add-extension
into 6e9f20d on typeorm:master.

gioboa
gioboa approved these changes Aug 15, 2025
View reviewed changes
Copy link
Collaborator

@gioboa gioboa left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution @wszgrcy

@alumni alumni changed the title docs: added "piying-orm" extension to readme docs: added piying-orm extension to readme Aug 16, 2025
@alumni alumni changed the title docs: added piying-orm extension to readme docs: added @piying/orm extension to readme Aug 16, 2025
@alumni alumni merged commit 0b767e8 into typeorm:master Aug 16, 2025
56 checks passed
ThbltLmr pushed a commit to ThbltLmr/typeorm that referenced this pull request Dec 2, 2025
@wszgrcy @ThbltLmr
docs: added @piying/orm extension to readme (typeorm#11596)
01699c0 
* docs: added "piying-orm" extension to readme

* docs: added "piying-orm" extension to readme
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@naorpeled naorpeled naorpeled approved these changes

@gioboa gioboa gioboa approved these changes

+1 more reviewer

@coderabbitai coderabbitai[bot] coderabbitai[bot] left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@wszgrcy @coveralls @naorpeled @gioboa @alumni