uber/NullAway

Disallow writing `@Initializer` on constructors

Open

#540 创建于 2022年1月6日

在 GitHub 查看
 (0 评论) (0 反应) (0 负责人)Java (3,462 star) (288 fork)batch import
good first issue

描述

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.

贡献者指南

技术栈
java
领域
backendtooling
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Javaannotation processing basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
55
研究方向
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.