feat: rename the project to Pangular Inspector - #212
erkamyaman wants to merge 1 commit into
Conversation
The project is now Pangular Inspector, the unified Angular devtools. User-facing text in the panel, popup, extension, MCP name and docs says Pangular Inspector, the package is @pangular-inspector/core (a placeholder until the final name is picked in santoshyadavdev#211) and the CLI command is pangular. Internal identifiers such as RPC names, globals and config names stay as they are.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. 🧰 Additional context used📚 Code guidelines (1)No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
⛔ Files ignored due to path filters (3)
📒 Files selected for processing (93)
Included review availability: This review used your included allowance. 1 included review remains after this review. Your included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour. 📝 WalkthroughWalkthroughThe repository changes its product branding to Pangular Inspector. The npm package scope changes to ChangesPangular Inspector rebrand
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~12 minutes Change: Other Suggested labels: Merge Risk: ⚪ Minimal · up to The package, CLI, runtime labels, and documentation use the new branding. The checked-in extension assets are present and consistent, and no merge blocker remains. 🚥 Pre-merge checks | ✅ 3 | ❌ 1 | ❓ 1❌ Failed checks (1 warning, 1 inconclusive)
✅ Passed checks (3 passed)
Full details: Linked Issues checkExplanation The changes update product wording across source strings, extension metadata, documentation, examples, package references, and CLI tests, which supports the rename in [ Full details: Docstring CoverageExplanation Docstring coverage is 44.44% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 18 functions across 40 files. (53 skipped: 53 unsupported.)
✨ Finishing Touches🧪 Generate unit tests (beta)
A rabbit checks the new name bright Comment |
|
View your CI Pipeline Execution ↗ for commit ebbd967
💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗ ☁️ Nx Cloud last updated this comment at |
What and why
The project is now Pangular Inspector, the unified Angular devtools (decided in #17).
@santoshyadavdev/ng-devtoolsbecomes@pangular-inspector/corein every import, example, script and doc. This is a placeholder until the final name is picked in Finish the Pangular Inspector rename: package name, MCP name and leftover ng-devtools text #211. Nothing has been published under the org yet.pangular(npx @pangular-inspector/core dev), with the bannerpangular v<version>.ng-devtools:*RPC and tool names,__ng-devtoolsURLs,window.__ngDevtools*globals,NgDevtools*APIs, config and env var names, the folder, repo and docs URL), the MCP server name in the setup samples, and some casual "ng-devtools" text. All listed in Finish the Pangular Inspector rename: package name, MCP name and leftover ng-devtools text #211. The one mention of Google's official Angular DevTools extension stays.Closes #208
How it was verified
pnpm commit:checkpnpm format:checkpnpm typecheckpnpm test:devtoolsandpnpm test:panelpnpm skills:checkapps/docsupdated andpnpm docs:buildpassespnpm extension:buildandextension/uicommittedpnpm test:axepassespangular --help,--versionand thedevbanner checked;npm pack --dry-rungivespangular-inspector-core-0.0.6.tgzwithpangularas its only binNotes for reviewers
This touches many files and will conflict with the open drafts #195, #190 and #21 where they mention the package name or CLI. Whichever lands second needs a quick update.
Summary by CodeRabbit
@pangular-inspector/coreand thepangularCLI.