chore(plugin): add inertia 3 plugin to registry#420
chore(plugin): add inertia 3 plugin to registry#420SantosVilanculos wants to merge 1 commit intoTanStack:mainfrom
Conversation
📝 WalkthroughWalkthroughA new Inertia 3 devtools plugin ( Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
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
📒 Files selected for processing (2)
.changeset/wild-papayas-judge.mdpackages/devtools/src/tabs/plugin-registry.ts
| '@tanstack/devtools': patch | ||
| --- | ||
|
|
||
| Add inertia 3 devtool to registry |
There was a problem hiding this comment.
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)', |
There was a problem hiding this comment.
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.
| 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.
🎯 Changes
✅ Checklist
pnpm test:pr.🚀 Release Impact
Summary by CodeRabbit