Skip to content

docs(proposals): P-026 unneeded-dependency profile (Own.Lean) - #180

Closed
PhysShell wants to merge 2 commits into
mainfrom
claude/you-dont-need-proposal-5p7vs9
Closed

docs(proposals): P-026 unneeded-dependency profile (Own.Lean)#180
PhysShell wants to merge 2 commits into
mainfrom
claude/you-dont-need-proposal-5p7vs9

Conversation

@PhysShell

Copy link
Copy Markdown
Owner

Что и зачем

Добавляет P-026 — предложение по профилю проверок «you don't need this abstraction»
(Own.Lean), вдохновлённое мета-списком you-dont-need/You-Dont-Need, но
намеренно ограниченное доказуемыми находками на конкретном call site (тривиальный
1:1 AutoMapper-профиль, MediatR-хэндлер с единственной реализацией и без
pipeline behaviours), а не мнением о библиотеке как таковой.

Тип изменения

  • feat — новая возможность
  • fix — исправление бага
  • docs — документация
  • refactor / chore / test / ci — без изменения поведения

Как проверено

Только markdown-документация (новый docs/proposals/P-026-...md + записи в
индексах docs/proposals/README.md и docs/ROADMAP.md), кода не затронуто —
тестов/линтеров не требуется.

Связанные issue

Нет.

Чеклист

  • изменение покрыто тестом/селфтестом (или объяснено, почему нет) — только доки, тест не применим
  • README/docs обновлены при необходимости — индексы docs/proposals/README.md и docs/ROADMAP.md обновлены
  • коммиты в conventional-commit стиле (feat:, fix:, docs: …)

Generated by Claude Code

Evidence-only "you don't need this abstraction" checks, inspired by the
you-dont-need/You-Dont-Need meta-list but scoped away from opinion: each
finding names a call site with zero customization evidence (a trivial
AutoMapper 1:1 profile, a MediatR handler with one impl and no pipeline
behaviours) rather than judging a library's presence. Report-only,
never a build gate; bounded against P-021 (async elision already owned
by ASYNC040) and P-023 (Own.Arch gates forbidden structure, this flags
redundant structure).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NNLSE5z4V92RwdHHF1mW45
@coderabbitai

coderabbitai Bot commented Jul 5, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@PhysShell, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 7b9e1367-774a-43d0-a7bf-98898d831d49

📥 Commits

Reviewing files that changed from the base of the PR and between 5ea68da and 9cd10b8.

📒 Files selected for processing (3)
  • docs/ROADMAP.md
  • docs/proposals/P-026-unneeded-dependency-profile.md
  • docs/proposals/README.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch claude/you-dont-need-proposal-5p7vs9

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.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 01ff4b8291

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/proposals/P-026-unneeded-dependency-profile.md Outdated
… reuse

Codex review on #180 caught it: the extractor's DiTypeName collapses
IRequestHandler<Foo,Bar> to the bare IRequestHandler identifier, so the
existing P-006 services[] graph can't distinguish per-request-type
implementation counts once a project has more than one MediatR handler.
Correct the MVP scope and sketch to require a small additive extractor
change that preserves closed generic arguments for MediatR marker
interfaces, instead of claiming YDN002 rides the graph as-is.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NNLSE5z4V92RwdHHF1mW45

Copy link
Copy Markdown
Owner Author

Консолидировано в #190 (перенумеровано P-026 → P-028-unneeded-dependency-profile из-за коллизии номеров). Закрываю в пользу единого PR.


Generated by Claude Code

@PhysShell PhysShell closed this Jul 8, 2026
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.

2 participants