Skip to content

docs: v1#401

Merged
dinwwwh merged 13 commits intomainfrom
docs/v1
Apr 15, 2025
Merged

docs: v1#401
dinwwwh merged 13 commits intomainfrom
docs/v1

Conversation

@dinwwwh
Copy link
Copy Markdown
Member

@dinwwwh dinwwwh commented Apr 12, 2025

Summary by CodeRabbit

  • New Features

    • Added a blog section to the documentation site, including a v1 announcement post and navigation updates.
  • Documentation

    • Streamlined and updated the "Highlights" sections across all README files for improved clarity and conciseness.
    • Revised homepage and feature descriptions for a more concise presentation.
    • Enhanced the comparison table with direct documentation links and refined feature wording.
  • Style

    • Updated emoji usage and reordered feature lists for a more consistent and visually appealing documentation format.

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 12, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
orpc ✅ Ready (Inspect) Visit Preview 💬 Add feedback Apr 15, 2025 2:16pm

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 12, 2025

Caution

Review failed

The pull request is closed.

Walkthrough

This update focuses on documentation and configuration improvements across the oRPC project. The "Highlights" sections in multiple README files were streamlined for conciseness, with shorter, emoji-prefixed bullet points, and some features or descriptive phrases were removed or reworded. Site configuration was updated to add a blog section, including a new announcement post for oRPC v1. The homepage and comparison documentation were revised for clarity and brevity, with added direct documentation links in the comparison table. No changes were made to code functionality or exported entities; all modifications are limited to documentation, markdown content, and configuration files.

Changes

Files/Paths Change Summary
README.md, packages/*/README.md Revised "Highlights" sections: replaced longer, descriptive bullet points with concise, emoji-prefixed lists; removed or merged some features (e.g., "Exceptional Developer Experience," "Fast & Lightweight," "Reusability," "Simplicity"); reordered and rephrased remaining highlights for clarity and uniformity; shortened introductory sentences. No technical or functional content changes.
apps/content/.vitepress/config.ts Updated site configuration: shortened site title and description, added "Blog" to navigation bar, and introduced a sidebar entry for the blog section. No logic or behavior changes.
apps/content/blog/v1-announcement.md Added a new blog post announcing oRPC v1: describes project motivation, development journey, feature highlights, comparative benchmarks, and acknowledgements.
apps/content/docs/comparison.md Expanded and refined the comparison table: added a column linking to oRPC documentation for each feature, clarified feature names/descriptions, increased granularity for OpenAPI-related features, and adjusted some support indicators.
apps/content/index.md Updated homepage content: added a description field, removed an Open Graph meta tag, shortened the hero tagline, revised and reordered feature highlights for conciseness, and unified tone. No code or logic changes.

Possibly related PRs

  • docs: v1 #401: Also updates README and documentation files by simplifying and reformatting the "Highlights" sections across multiple packages and the main README, closely related in scope and content.

Poem

🐇✨

With highlights trimmed and features neat,
Emojis lead each bullet beat.
A blog appears, the news is spread—
oRPC v1 has forged ahead!
Docs now gleam with links and cheer,
Simpler words, the path is clear.
In every README, rabbits dance—
Type-safe joy at every glance!

📝🚀


📜 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 85c67e6 and b64c935.

📒 Files selected for processing (1)
  • apps/content/blog/v1-announcement.md (1 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.

@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 12, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

📢 Thoughts on this report? Let us know!

@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented Apr 12, 2025

More templates

@orpc/arktype

npm i https://pkg.pr.new/@orpc/arktype@401

@orpc/client

npm i https://pkg.pr.new/@orpc/client@401

@orpc/contract

npm i https://pkg.pr.new/@orpc/contract@401

@orpc/openapi

npm i https://pkg.pr.new/@orpc/openapi@401

@orpc/openapi-client

npm i https://pkg.pr.new/@orpc/openapi-client@401

@orpc/react

npm i https://pkg.pr.new/@orpc/react@401

@orpc/react-query

npm i https://pkg.pr.new/@orpc/react-query@401

@orpc/server

npm i https://pkg.pr.new/@orpc/server@401

@orpc/solid-query

npm i https://pkg.pr.new/@orpc/solid-query@401

@orpc/shared

npm i https://pkg.pr.new/@orpc/shared@401

@orpc/standard-server

npm i https://pkg.pr.new/@orpc/standard-server@401

@orpc/standard-server-fetch

npm i https://pkg.pr.new/@orpc/standard-server-fetch@401

@orpc/standard-server-node

npm i https://pkg.pr.new/@orpc/standard-server-node@401

@orpc/svelte-query

npm i https://pkg.pr.new/@orpc/svelte-query@401

@orpc/valibot

npm i https://pkg.pr.new/@orpc/valibot@401

@orpc/vue-colada

npm i https://pkg.pr.new/@orpc/vue-colada@401

@orpc/vue-query

npm i https://pkg.pr.new/@orpc/vue-query@401

@orpc/zod

npm i https://pkg.pr.new/@orpc/zod@401

commit: b64c935

@dinwwwh dinwwwh marked this pull request as ready for review April 15, 2025 13:59
Copy link
Copy Markdown

@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

🧹 Nitpick comments (1)
apps/content/blog/v1-announcement.md (1)

132-132: Accessibility: Add alt text to sponsor image.

Add descriptive alt text to the sponsor image for accessibility.

-    <img src='https://cdn.jsdelivr.net/gh/unnoq/unnoq/sponsors.svg'/>
+    <img src='https://cdn.jsdelivr.net/gh/unnoq/unnoq/sponsors.svg' alt="oRPC sponsors"/>
🧰 Tools
🪛 markdownlint-cli2 (0.17.2)

132-132: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between f81b4a2 and 85c67e6.

⛔ Files ignored due to path filters (1)
  • apps/content/public/og.jpg is excluded by !**/*.jpg
📒 Files selected for processing (23)
  • README.md (1 hunks)
  • apps/content/.vitepress/config.ts (3 hunks)
  • apps/content/blog/v1-announcement.md (1 hunks)
  • apps/content/docs/comparison.md (1 hunks)
  • apps/content/index.md (2 hunks)
  • packages/arktype/README.md (1 hunks)
  • packages/client/README.md (1 hunks)
  • packages/contract/README.md (1 hunks)
  • packages/openapi-client/README.md (1 hunks)
  • packages/openapi/README.md (1 hunks)
  • packages/react-query/README.md (1 hunks)
  • packages/react/README.md (1 hunks)
  • packages/server/README.md (1 hunks)
  • packages/shared/README.md (1 hunks)
  • packages/solid-query/README.md (1 hunks)
  • packages/standard-server-fetch/README.md (1 hunks)
  • packages/standard-server-node/README.md (1 hunks)
  • packages/standard-server/README.md (1 hunks)
  • packages/svelte-query/README.md (1 hunks)
  • packages/valibot/README.md (1 hunks)
  • packages/vue-colada/README.md (1 hunks)
  • packages/vue-query/README.md (1 hunks)
  • packages/zod/README.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
packages/shared/README.md

[misspelling] ~38-~38: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/openapi-client/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/standard-server-fetch/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/arktype/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/valibot/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/svelte-query/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/standard-server/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/server/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/solid-query/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/standard-server-node/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/zod/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/contract/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/vue-colada/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/react/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/openapi/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/client/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

apps/content/blog/v1-announcement.md

[grammar] ~9-~9: The verb form seems incorrect.
Context: ...build type-safe APIs with TypeScript. It's has own goal but can fairly be compared to ...

(IS_VBZ)


[misspelling] ~71-~71: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)


[uncategorized] ~128-~128: “you” seems less likely than “you’re” (you are).
Context: ...sponsor (private) to start my story If you interested in sponsoring oRPC, you can ...

(AI_HYDRA_LEO_CP_YOU_YOUARE)

packages/react-query/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/vue-query/README.md

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

🪛 markdownlint-cli2 (0.17.2)
apps/content/blog/v1-announcement.md

132-132: Images should have alternate text (alt text)
null

(MD045, no-alt-text)

🔇 Additional comments (31)
apps/content/.vitepress/config.ts (1)

8-9: Documentation site configuration and navigation improvements look good.

The updates to the title, description, and addition of the blog navigation/sidebar are clear and beneficial for documentation discoverability.

Also applies to: 53-54, 208-210

packages/openapi-client/README.md (1)

24-41: Streamlined highlights section is clear and consistent.

The reworded highlights improve readability and maintain consistency across documentation. No issues found.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/svelte-query/README.md (1)

24-41: Documentation highlights are now more concise and consistent.

The updated highlights section is clear and matches the style across the project. No issues detected.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/shared/README.md (1)

29-46: Documentation highlights are now more concise and unified.

The reformatted highlights section improves clarity and consistency across the monorepo. No issues found.

🧰 Tools
🪛 LanguageTool

[misspelling] ~38-~38: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/solid-query/README.md (1)

24-41: Highlights section is now more concise and consistent.

The updated highlights section is clear and matches the documentation style across the project. No issues detected.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

README.md (2)

30-41: Documentation improvements look great!

The streamlined highlights section is clear, concise, and consistent with modern documentation standards. No issues found.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)


33-33: Skip false positive spelling warning.

"Pinia Colada" is a valid library name; the static analysis warning can be safely ignored.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/contract/README.md (2)

30-41: Concise highlights improve readability.

The updated highlights section is succinct and accurately reflects the package's features.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)


33-33: Skip false positive spelling warning.

"Pinia Colada" is correct; no action needed.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/server/README.md (2)

30-41: Highlights section is now clearer and more concise.

The documentation update is well-executed and aligns with best practices.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)


33-33: Skip false positive spelling warning.

No correction needed for "Pinia Colada".

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/arktype/README.md (2)

30-41: Streamlined highlights section is effective.

The new highlights are concise and accurately describe the package's strengths.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)


33-33: Skip false positive spelling warning.

"Pinia Colada" is a valid name; no changes needed.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/standard-server-fetch/README.md (2)

30-41: Documentation highlights are now clearer and more concise.

The changes improve readability and maintain consistency across the project.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)


33-33: Skip false positive spelling warning.

No correction needed for "Pinia Colada".

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/valibot/README.md (1)

30-41: Documentation update looks good.

The revised "Highlights" section is concise, clear, and free of spelling or grammar issues. No action needed.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/client/README.md (1)

30-41: Documentation update looks good.

The "Highlights" section is now more concise and accurate. No spelling or grammar issues found.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/vue-query/README.md (1)

30-41: Documentation update looks good.

The "Highlights" section is concise and accurate. No spelling or grammar issues found.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/zod/README.md (1)

30-41: Documentation update looks good.

The "Highlights" section is concise and accurate. No spelling or grammar issues found.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/vue-colada/README.md (1)

30-41: Documentation update looks good.

The "Highlights" section is concise and accurate. No spelling or grammar issues found.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

apps/content/index.md (1)

1-65: Documentation and presentation changes look great.

The homepage content is now more concise and unified. No issues found.

packages/react-query/README.md (2)

24-41: Documentation improvements are clear and consistent.

The highlights are now more concise and readable. No issues found.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)


33-33: No spelling error—product names are correct.

"TanStack" and "Colada" are valid product names; the static analysis warning can be ignored.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/standard-server/README.md (2)

24-41: Documentation changes are clear and consistent.

The highlights are now more concise and unified with the rest of the project. No issues found.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)


33-33: No spelling error—product names are correct.

"TanStack" and "Colada" are valid product names; the static analysis warning can be ignored.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/openapi/README.md (2)

24-41: Documentation changes are clear and consistent.

The highlights are now more concise and unified with the rest of the project. No issues found.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)


33-33: No spelling error—product names are correct.

"TanStack" and "Colada" are valid product names; the static analysis warning can be ignored.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/standard-server-node/README.md (2)

24-41: Documentation changes are clear and consistent.

The highlights are now more concise and unified with the rest of the project. No issues found.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)


33-33: No spelling error—product names are correct.

"TanStack" and "Colada" are valid product names; the static analysis warning can be ignored.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

packages/react/README.md (1)

24-41: Highlights section is concise and well-structured.

The revised highlights are clear, consistent, and use appropriate terminology for the target audience. No issues found.

🧰 Tools
🪛 LanguageTool

[misspelling] ~33-~33: Possible spelling mistakes found.
Context: ...tack Query (React, Vue, Solid, Svelte), Pinia Colada, and more. - 🚀 Server Actions: Ful...

(EN_MULTITOKEN_SPELLING_TWO)

apps/content/docs/comparison.md (1)

14-38: Comparison table improvements are clear and helpful.

The addition of direct documentation links and refined feature names enhances usability and clarity. No issues found.

Comment thread apps/content/blog/v1-announcement.md Outdated
- [Robbe95](https://github.com/Robbe95)
- And my first sponsor (private) to start my story

If you interested in sponsoring oRPC, you can do it [here](https://github.com/sponsors/unnoq).
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue

Grammar correction: "If you interested" → "If you're interested".

Change "If you interested in sponsoring oRPC, you can do it here" to "If you're interested in sponsoring oRPC, you can do it here".

-If you interested in sponsoring oRPC, you can do it [here](https://github.com/sponsors/unnoq).
+If you're interested in sponsoring oRPC, you can do it [here](https://github.com/sponsors/unnoq).
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
If you interested in sponsoring oRPC, you can do it [here](https://github.com/sponsors/unnoq).
If you're interested in sponsoring oRPC, you can do it [here](https://github.com/sponsors/unnoq).
🧰 Tools
🪛 LanguageTool

[uncategorized] ~128-~128: “you” seems less likely than “you’re” (you are).
Context: ...sponsor (private) to start my story If you interested in sponsoring oRPC, you can ...

(AI_HYDRA_LEO_CP_YOU_YOUARE)

Comment thread apps/content/blog/v1-announcement.md Outdated

# oRPC v1 Announcement - Typesafe APIs Made Simple 🪄

oRPC is a thing help you build type-safe APIs with TypeScript. It's has own goal but can fairly be compared to other libraries like tRPC, ts-rest, next-safe-action, etc. or even alternative them.
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue

Grammar correction needed in introduction.

Change "It's has own goal but can fairly be compared..." to "It has its own goal but can fairly be compared...".

-oRPC is a thing help you build type-safe APIs with TypeScript. It's has own goal but can fairly be compared to other libraries like tRPC, ts-rest, next-safe-action, etc. or even alternative them.
+oRPC is a tool to help you build type-safe APIs with TypeScript. It has its own goal but can fairly be compared to other libraries like tRPC, ts-rest, next-safe-action, etc., or even serve as an alternative to them.
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
oRPC is a thing help you build type-safe APIs with TypeScript. It's has own goal but can fairly be compared to other libraries like tRPC, ts-rest, next-safe-action, etc. or even alternative them.
oRPC is a tool to help you build type-safe APIs with TypeScript. It has its own goal but can fairly be compared to other libraries like tRPC, ts-rest, next-safe-action, etc., or even serve as an alternative to them.
🧰 Tools
🪛 LanguageTool

[grammar] ~9-~9: The verb form seems incorrect.
Context: ...build type-safe APIs with TypeScript. It's has own goal but can fairly be compared to ...

(IS_VBZ)

@dinwwwh dinwwwh merged commit c788572 into main Apr 15, 2025
4 of 6 checks passed
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.

1 participant