uber/NullAway

Disallow writing `@Initializer` on constructors

已關閉

#540 建立於 2022年1月6日

在 GitHub 查看貢獻者指南
 (0 則留言) (0 個反應) (0 位負責人)Java (288 個分叉)batch import
good first issue

倉庫指標

星標
 (3,462 顆星)
PR 合併指標
 (平均合併 3天 23小時) (30 天內合併 14 個 PR)

描述

If a constructor is annotated with @Initializer, NullAway currently treats the constructor as if it were an initializer method that runs after any constructor, which clearly doesn't make sense. Instead, NullAway should report an error, as this is an invalid use of @Initializer.

貢獻者指南

研究方向
Look at NullAway's source code to understand how `@Initializer` is currently validated, likely in a handler or checker class. Examine existing checks for invalid annotation usage patterns, such as `@NonNull` on primitives. Add a new check that detects when `@Initializer` is applied to a constructor and reports an error. Consider writing a unit test to verify the behavior. Refer to issue #540 and the file `com/uber/nullaway/NullAway.java` or similar.
技術棧
java
領域
backendtooling
議題類型
錯誤
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
半天
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
新近可參與
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
清晰
前置要求
Javaannotation processing basics
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
55