Unstable API Usage
Reports usages of an API marked with one of the annotations as unstable. Such an API may be changed or removed in future versions, breaking the code that uses it.
Locating this inspection
- By ID
Can be used to locate inspection in e.g. Qodana configuration files, where you can quickly enable or disable it, or adjust its settings.
UnstableApiUsage- Via Settings dialog
Path to the inspection settings via IntelliJ Platform IDE Settings dialog, when you need to adjust inspection settings directly from your IDE.
The annotations which are used to mark unstable APIs are shown in the list below.
By default, the inspection ignores usages of unstable APIs if their declarations are located in sources of the same project. In such cases it'll be possible to update the usages when you change APIs. However, it may be inconvenient if the project is big, so one can switch off the Ignore API declared in this project option to report the usages of unstable APIs declared in both the project sources and libraries.
Inspection options
Here you can find the description of settings available for the Unstable API Usage inspection, and the reference of their default values.
- Ignore inside imports
Default: Selected
- Ignore API declared in this project
Default: Selected
- Unstable API annotations
[org.jetbrains.annotations.ApiStatus.ScheduledForRemoval, org.jetbrains.annotations.ApiStatus.Experimental, org.jetbrains.annotations.ApiStatus.Internal, com.google.common.annotations.Beta, io.reactivex.annotations.Beta, io.reactivex.annotations.Experimental, rx.annotations.Experimental, rx.annotations.Beta, org.apache.http.annotation.Beta, org.gradle.api.Incubating]
Availability
- By default bundled with
- Can be installed with plugin
Java, 241.18072