2825ece820
while some of these may of been true, they are extreme cases and cause a ton of noise to plugin developers. Use ApiStatus.Internal instead of Deprecated for actual internal API that continues to have use (internally). These do not help plugin developers if they bring moise noise than value.
30 lines
885 B
Java
30 lines
885 B
Java
package org.bukkit;
|
|
|
|
import java.lang.annotation.Retention;
|
|
import java.lang.annotation.RetentionPolicy;
|
|
import org.jetbrains.annotations.ApiStatus;
|
|
|
|
/**
|
|
* Annotation for types, whose nullability is not well defined, so
|
|
* {@link org.jetbrains.annotations.NotNull} nor
|
|
* {@link org.jetbrains.annotations.Nullable} is applicable. For example when
|
|
* interface defines a method, whose nullability depends on the implementation.
|
|
*
|
|
* @deprecated This should generally not be used in any new API code as it
|
|
* suggests a bad API design.
|
|
*/
|
|
@Retention(RetentionPolicy.CLASS)
|
|
@java.lang.annotation.Documented // Paper
|
|
@ApiStatus.Internal
|
|
@Deprecated(since = "1.13.2")
|
|
public @interface UndefinedNullability {
|
|
|
|
/**
|
|
* Human readable description of the circumstances, in which the type is
|
|
* nullable.
|
|
*
|
|
* @return description
|
|
*/
|
|
String value() default "";
|
|
}
|