Conversation
…on-mode fix: restore inline popup in production builds
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
Thank you for creating this pull request and helping make the project better. We will review / merge it when we are online. |
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThe PR changes content-script URL scoping, applies mode-specific matches during manifest generation, adds manifest-scope validation for generated outputs, and runs the production check in CI for ChangesProduction manifest validation
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant CIWorkflow
participant ExtensionBuild
participant ManifestVerifier
participant OutputDirectory
CIWorkflow->>ExtensionBuild: Build production extension
ExtensionBuild->>OutputDirectory: Write manifest.json
CIWorkflow->>ManifestVerifier: Verify production Chrome scope
ManifestVerifier->>OutputDirectory: Read and validate manifests
ManifestVerifier-->>CIWorkflow: Report success or set failure status
Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
|
Overall Grade |
Security Reliability Complexity Hygiene |
Code Review Summary
| Analyzer | Status | Updated (UTC) | Details |
|---|---|---|---|
| JavaScript | Jul 23, 2026 4:21a.m. | Review ↗ |
Important
AI Review is run only on demand for your team. We're only showing results of static analysis review right now. To trigger AI Review, comment @deepsourcebot review on this thread.
eplus-bot
left a comment
There was a problem hiding this comment.
Approved by @eplus-bot after all pull request checks passed.
CI run: https://github.com/ePlus-DEV/gmail-alias-toolkit/actions/runs/29979273011
|
Approved by @eplus-bot after all pull request checks passed. Approval refresh: #5 CI run: https://github.com/ePlus-DEV/gmail-alias-toolkit/actions/runs/30012127562 |
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
wxt.config.ts (1)
14-14: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low valueDocument the newly added arrow callbacks.
vite,build:manifestGenerated, and thefind/somepredicates lack the required one-line JSDoc. Extract the predicates into documented helpers where needed.As per coding guidelines, every function declaration, arrow function, and exported component must have at least a one-line JSDoc comment describing its purpose.
Also applies to: 46-52
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@wxt.config.ts` at line 14, Document every newly added callback in the configuration, including the vite and build:manifestGenerated arrow callbacks and the predicates used by find and some. Add one-line JSDoc descriptions directly above callbacks where possible, and extract the find/some predicates into named documented helpers when required; preserve their existing behavior.Source: Coding guidelines
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@scripts/verify-manifest-scope.mjs`:
- Around line 79-102: Update the validation logic in verify-manifest-scope
around contentScriptMatches and grantedHosts to reject any URL pattern not
included in DEV_SITES. Preserve the existing checks for missing DEV_SITES
entries and literal ALL_URLS, while ensuring both sets contain only the
development allowlist so broad patterns such as *://*/* fail validation.
- Around line 114-124: Update the manifest scope validation before the
mode-specific calls to select only the generated inline helper content script
identified by the corresponding configuration entry in wxt.config.ts, and derive
contentScriptMatches from that script’s matches rather than flattening every
manifest.content_scripts entry. Preserve the existing grantedHosts construction
and validateDevelopmentScope/validateProductionScope flow.
---
Nitpick comments:
In `@wxt.config.ts`:
- Line 14: Document every newly added callback in the configuration, including
the vite and build:manifestGenerated arrow callbacks and the predicates used by
find and some. Add one-line JSDoc descriptions directly above callbacks where
possible, and extract the find/some predicates into named documented helpers
when required; preserve their existing behavior.
🪄 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 Plus
Run ID: 01f59d6e-1972-44a2-b695-4a28b08bc609
📒 Files selected for processing (4)
.github/workflows/ci.ymlentrypoints/content/index.tsscripts/verify-manifest-scope.mjswxt.config.ts
🚧 Files skipped from review as they are similar to previous changes (1)
- .github/workflows/ci.yml
eplus-bot
left a comment
There was a problem hiding this comment.
Approved by @eplus-bot after all pull request checks passed.
CI run: https://github.com/ePlus-DEV/gmail-alias-toolkit/actions/runs/29989378303
…owlist fix: restrict development manifest to allowlisted sites
eplus-bot
left a comment
There was a problem hiding this comment.
Approved by @eplus-bot after all pull request checks passed.
CI run: https://github.com/ePlus-DEV/gmail-alias-toolkit/actions/runs/30006049395
eplus-bot
left a comment
There was a problem hiding this comment.
Approved by @eplus-bot after all pull request checks passed.
CI run: https://github.com/ePlus-DEV/gmail-alias-toolkit/actions/runs/30006479333
eplus-bot
left a comment
There was a problem hiding this comment.
Approved by @eplus-bot after all pull request checks passed.
CI run: https://github.com/ePlus-DEV/gmail-alias-toolkit/actions/runs/30012127562
|
@eplus-bot review |
eplus-bot
left a comment
There was a problem hiding this comment.
Approved by @eplus-bot after all checks passed for commit 37231c6c8660771936dfa87b4c4cc03a87c3a0ef.
|
✅ eplus-bot reviewed and approved commit |
Summary
Fix WXT manifest scope handling and validation for the inline helper content script.
Type of Change
Areas Touched
Testing
yarn compileyarn testyarn buildUnit-test coverage added
The manifest validator now has regression coverage for:
permissions;*://*/*;<all_urls>rejection in development;Screenshots or Recording
N/A — no UI changes.
Notes for Reviewers
Production validation targets only the generated inline helper entry (
content-scripts/content.js) instead of flattening matches from every manifest content script. Development scope remains restricted to the configured allowlist. Tests import the validator constants directly to avoid fixture drift.