Skip to content

chore(plugin): add inertia 3 plugin to registry#420

Open
SantosVilanculos wants to merge 1 commit intoTanStack:mainfrom
SantosVilanculos:inertia-3-plugin
Open

chore(plugin): add inertia 3 plugin to registry#420
SantosVilanculos wants to merge 1 commit intoTanStack:mainfrom
SantosVilanculos:inertia-3-plugin

Conversation

@SantosVilanculos
Copy link
Copy Markdown

@SantosVilanculos SantosVilanculos commented Apr 8, 2026

🎯 Changes

✅ Checklist

  • I have followed the steps in the Contributing guide.
  • I have tested this code locally with pnpm test:pr.

🚀 Release Impact

  • This change affects published code, and I have generated a changeset.
  • This change is docs/CI/dev-only (no release).

Summary by CodeRabbit

  • New Features
    • Added a new Inertia 3 devtool plugin to the devtools registry. This plugin provides specialized development tools and monitoring capabilities for React applications built with Inertia 3 and Laravel, enhancing debugging and optimization during development.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Apr 8, 2026

📝 Walkthrough

Walkthrough

A new Inertia 3 devtools plugin (@santosvilanculos/bevor-react) is added to the plugin registry, with a corresponding changeset file documenting the patch-level release to @tanstack/devtools.

Changes

Cohort / File(s) Summary
Changeset Documentation
.changeset/wild-papayas-judge.md
Patch-level release entry for @tanstack/devtools documenting the addition of Inertia 3 devtool to registry.
Plugin Registry
packages/devtools/src/tabs/plugin-registry.ts
New plugin entry for @santosvilanculos/bevor-react with metadata including display title, plugin import configuration, framework (react), author information, documentation/logo/repository URLs, and classification tags (TanStack, React, Inertia, Laravel).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A new plugin hops into the registry today,
Inertia 3 devtools leading the way,
With React and Laravel in perfect accord,
The changelog sings, our hearts are restored! ✨

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: adding an Inertia 3 plugin to the registry, which matches the file modifications.
Description check ✅ Passed The description follows the template structure with all required sections present, including Changes, Checklist, and Release Impact sections with appropriate checkboxes marked.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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

@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

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.changeset/wild-papayas-judge.md:
- Line 5: Update the release note text that currently reads "Add inertia 3
devtool to registry" to the consistent product-cased and pluralized phrasing
"Add Inertia 3 devtools plugin to the registry" so it matches existing
terminology and casing conventions.

In `@packages/devtools/src/tabs/plugin-registry.ts`:
- Line 278: The plugin metadata currently contains a personal email in the
author field ("author: 'Santos Vilanculos (santosvilanculos@yahoo.com)')");
remove the direct email and leave only a name or handle (e.g., "Santos
Vilanculos" or "santosvilanculos") in the author value in
packages/devtools/src/tabs/plugin-registry.ts (the author metadata entry) to
avoid publishing PII; update any other occurrences of the same author string in
the file if present and run tests/build to verify no metadata consumers rely on
the email.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 328af115-2aae-47f4-a912-d33df4b730e8

📥 Commits

Reviewing files that changed from the base of the PR and between f1844a2 and 7e28731.

📒 Files selected for processing (2)
  • .changeset/wild-papayas-judge.md
  • packages/devtools/src/tabs/plugin-registry.ts

'@tanstack/devtools': patch
---

Add inertia 3 devtool to registry
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 | 🟡 Minor

Polish release note wording for consistency.

Use product casing/plural form to match existing terminology: “Add Inertia 3 devtools plugin to the registry”.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.changeset/wild-papayas-judge.md at line 5, Update the release note text
that currently reads "Add inertia 3 devtool to registry" to the consistent
product-cased and pluralized phrasing "Add Inertia 3 devtools plugin to the
registry" so it matches existing terminology and casing conventions.

docsUrl:
'https://github.com/SantosVilanculos/bevor/tree/main/packages/react',
repoUrl: 'https://github.com/SantosVilanculos/bevor',
author: 'Santos Vilanculos (santosvilanculos@yahoo.com)',
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 | 🟠 Major

Remove direct email address from public plugin metadata.

Committing a personal email in author introduces unnecessary PII exposure in published artifacts. Prefer name/handle only.

🔧 Suggested change
-    author: 'Santos Vilanculos (santosvilanculos@yahoo.com)',
+    author: 'Santos Vilanculos (`@SantosVilanculos`)',
📝 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
author: 'Santos Vilanculos (santosvilanculos@yahoo.com)',
author: 'Santos Vilanculos (`@SantosVilanculos`)',
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@packages/devtools/src/tabs/plugin-registry.ts` at line 278, The plugin
metadata currently contains a personal email in the author field ("author:
'Santos Vilanculos (santosvilanculos@yahoo.com)')"); remove the direct email and
leave only a name or handle (e.g., "Santos Vilanculos" or "santosvilanculos") in
the author value in packages/devtools/src/tabs/plugin-registry.ts (the author
metadata entry) to avoid publishing PII; update any other occurrences of the
same author string in the file if present and run tests/build to verify no
metadata consumers rely on the email.

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