feat: new diagnostic MissingSuppressionComment - #4400
Conversation
|
Warning Review limit reached
Next review available in: 37 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the 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 configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (6)
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 |
|
|
||
| for (int i = 0; i < content.length; i++) { | ||
| var line = content[i].stripTrailing(); | ||
| if (!line.stripLeading().startsWith("//")) { |
There was a problem hiding this comment.
А почему висячие комментарии не проверяются?
| public class MissingSuppressionCommentDiagnostic extends AbstractDiagnostic { | ||
|
|
||
| /** Строка начинается с {@code // BSLLS:...-off} или {@code // BSLLS-off}. */ | ||
| private static final Pattern SUPPRESSION_PATTERN = Pattern.compile( |
There was a problem hiding this comment.
возможно вместо повторного парсинга имеет смысл заглянуть в DiagnosticIgnoranceData
|
|
||
| ## Особенности | ||
|
|
||
| - Диагностика сама **не подавляема** через `// BSLLS:MissingSuppressionComment-off` |
There was a problem hiding this comment.
Не увидел, где реализуется эта особенность
2 participants
Closes #2779. Finds BSLLS suppression comments without explanation.