Update component.md to explain it doesn't work in petite vue

[riderx]

Summary by CodeRabbit

• Documentation
  • Added a warning note in the advanced component guide clarifying that the described approach is not available in petite-vue-i18n.
  • Positioned the warning after the existing tip to improve visibility and reduce confusion when referencing global-scope suppression guidance.
  • Enhances clarity for users working with petite-vue-i18n by explicitly stating the limitation, preventing misconfiguration and saving troubleshooting time.

[coderabbitai]

Walkthrough

Documentation update: added a warning admonition to docs/guide/advanced/component.md noting unavailability in petite-vue-i18n. No code or API changes.

Changes

Cohort / File(s)	Summary
Docs update docs/guide/advanced/component.md	Inserted a :::warning NOTE stating “This is not available in petite-vue-i18n” after an existing tip; no runtime/code changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks (2 passed, 1 inconclusive)

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description Check	❓ Inconclusive	I’m unable to evaluate the pull request description because the current description text was not provided, so it’s unclear whether it accurately reflects the changes made to the documentation.	Please include the pull request’s description text so we can verify that it relates to the documentation change and adequately describes the added warning in component.md.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title “Update component.md to explain it doesn't work in petite vue” succinctly captures the main change of adding a warning to the component documentation about its unavailability in petite-vue-i18n, aligning directly with the modifications described in the changeset. It clearly identifies the file and the purpose of the update without extraneous details, making it easy for reviewers to understand the primary intent at a glance.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

Poem

A nibble of notes in the docs I write,
“Warning!” I thump with editorial might.
Petite-vue-i18n? Not here tonight—
Carrots of clarity, crisp and bright.
Hop along, ship strong, all changes light. 🥕🐇

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

docs/guide/advanced/component.md (1)

275-277: Clarify the unavailability and align admonition style.

Be explicit that the Translation component is the thing not supported, use code formatting for the package name, add a period, and consider using LIMITATION to match the earlier admonition style on Line 186. petite-vue-i18n officially omits the i18n-t component. (vue-i18n.intlify.dev, github.com)

-:::warning NOTE
-This is not available in petite-vue-i18n
+:::warning LIMITATION
+The Translation component (`i18n-t`) is not available in `petite-vue-i18n`.
 :::

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fdc9541 and 4eaddd3.

📒 Files selected for processing (1)

• docs/guide/advanced/component.md (1 hunks)