mirror of
https://gitflic.ru/project/openide/openide.git
synced 2025-12-16 22:51:17 +07:00
cleanup some inspection descriptions (IDEA-251455)
GitOrigin-RevId: 41a2012998f1342f484ade71639f587bf11caccc
This commit is contained in:
committed by
intellij-monorepo-bot
parent
41e0c1e038
commit
f2d0ec0156
@@ -1,10 +1,8 @@
|
|||||||
<html>
|
<html>
|
||||||
<body>
|
<body>
|
||||||
<p>
|
Reports classes, interfaces and methods that extend, implement or override API elements marked with an <code>@ApiStatus.NonExtendable</code>
|
||||||
Reports classes, interfaces and methods that extend, implement or override API elements marked with <code>@ApiStatus.NonExtendable</code>
|
annotation.
|
||||||
annotation.
|
An <code>@ApiStatus.NonExtendable</code> annotation indicates that the annotated API class, interface or method <strong>must not be extended,
|
||||||
</p>
|
|
||||||
<code>@ApiStatus.NonExtendable</code> annotation indicates that the annotated API class, interface or method <strong>must not be extended,
|
|
||||||
implemented or overridden</strong>. Instances of classes and interfaces marked with this annotation may be cast to an internal
|
implemented or overridden</strong>. Instances of classes and interfaces marked with this annotation may be cast to an internal
|
||||||
implementing class in the library code,
|
implementing class in the library code,
|
||||||
leading to <code>ClassCastException</code> if a different implementation is provided by client. New abstract methods may be added to such
|
leading to <code>ClassCastException</code> if a different implementation is provided by client. New abstract methods may be added to such
|
||||||
|
|||||||
@@ -1,10 +1,8 @@
|
|||||||
<html>
|
<html>
|
||||||
<body>
|
<body>
|
||||||
<p>
|
Reports calls to API methods marked with an <code>@ApiStatus.OverrideOnly</code> annotation.
|
||||||
Reports invocations of API methods marked with <code>@ApiStatus.OverrideOnly</code> annotation.
|
An <code>@ApiStatus.OverrideOnly</code> indicates that the annotated method is part of SPI (Service Provider Interface),
|
||||||
</p>
|
|
||||||
<code>@ApiStatus.OverrideOnly</code> indicates that the annotated method is part of SPI (Service Provider Interface),
|
|
||||||
which is intended to be <strong>only implemented or overridden</strong> but not called by clients of the declaring library.
|
which is intended to be <strong>only implemented or overridden</strong> but not called by clients of the declaring library.
|
||||||
If a class or interface is marked with this annotation it means that all its methods can be only overridden.
|
If a class or interface is marked with this annotation, it means that all its methods can be only overridden.
|
||||||
</body>
|
</body>
|
||||||
</html>
|
</html>
|
||||||
|
|||||||
@@ -1,5 +1,7 @@
|
|||||||
<html>
|
<html>
|
||||||
<body>
|
<body>
|
||||||
Reports usages of API marked with "unstable" annotations from the list below.
|
Reports usages of API marked as unstable with an annotation.
|
||||||
|
<!-- tooltip end -->
|
||||||
|
Use the list below to specify the annotations which mark an unstable API.
|
||||||
</body>
|
</body>
|
||||||
</html>
|
</html>
|
||||||
@@ -1,11 +1,11 @@
|
|||||||
<html>
|
<html>
|
||||||
<body>
|
<body>
|
||||||
<p>
|
Reports declarations of classes, methods and fields that reference an unstable API type in the signature,
|
||||||
Reports declarations of classes, methods and fields that reference an unstable API type in the signature
|
but are not marked with the same unstable annotation.
|
||||||
but are not marked with the same unstable annotation. Set of checked annotations' names is specified below.
|
|
||||||
</p>
|
|
||||||
This inspection may be useful to check that no <i>unstable (internal, experimental)</i> types are exposed in signatures of public API.
|
This inspection may be useful to check that no <i>unstable (internal, experimental)</i> types are exposed in signatures of public API.
|
||||||
For example, if an <i>experimental</i> class is used as the return type of a method, the method is also considered <i>experimental</i>
|
For example, if an <i>experimental</i> class is used as the return type of a method, the method is also considered <i>experimental</i>
|
||||||
because incompatible changes of the type (deletion or move to another package) lead to incompatible method signature changes.
|
because incompatible changes of the type (deletion or move to another package) lead to incompatible method signature changes.
|
||||||
|
<!-- tooltip end -->
|
||||||
|
Use the list below to specify the annotations which mark an unstable API.
|
||||||
</body>
|
</body>
|
||||||
</html>
|
</html>
|
||||||
@@ -1,7 +1,8 @@
|
|||||||
<html>
|
<html>
|
||||||
<body>
|
<body>
|
||||||
<p>Report meta annotations which are used by frameworks by reflection but their retention policy is not RUNTIME.
|
Reports meta annotations which are used via reflection by frameworks, but their retention policy is not RUNTIME.
|
||||||
If retention policy is missed, then default retention policy 'CLASS' would be used, which means that annotations by default are not visible at runtime</p>
|
If a retention policy is not specified, then the default retention policy 'CLASS' will be used.
|
||||||
|
Such annotations will not be visible at runtime.
|
||||||
<!-- tooltip end -->
|
<!-- tooltip end -->
|
||||||
<p><small>New in 2017.2</small></p>
|
<p><small>New in 2017.2</small></p>
|
||||||
</body>
|
</body>
|
||||||
|
|||||||
@@ -1,8 +1,7 @@
|
|||||||
<html>
|
<html>
|
||||||
<body>
|
<body>
|
||||||
<p>Reports a <b>null</b> check followed by a method call that will definitely return <b>false</b> when <b>null</b> is passed (e.g. <b>Class.isInstance</b>).
|
Reports a <b>null</b> check followed by a method call that will definitely return <b>false</b> when <b>null</b> is passed (e.g. <b>Class.isInstance</b>).
|
||||||
Such a check seems excessive as the method call always returns <b>false</b>.
|
Such a check seems excessive as the method call will always return <b>false</b> in this case.
|
||||||
</p>
|
|
||||||
<p>Here is an example of a violation: </p>
|
<p>Here is an example of a violation: </p>
|
||||||
<pre><code> if (x != null && myClass.isInstance(x)) { ... }</code></pre>
|
<pre><code> if (x != null && myClass.isInstance(x)) { ... }</code></pre>
|
||||||
<p>The quickfix changes this code to:</p>
|
<p>The quickfix changes this code to:</p>
|
||||||
|
|||||||
@@ -1,25 +1,6 @@
|
|||||||
<html>
|
<html>
|
||||||
<head>
|
|
||||||
<style type="text/css">
|
|
||||||
body, table {
|
|
||||||
font-family: Verdana, sans-serif;
|
|
||||||
font-size: 100%;
|
|
||||||
padding-left: 2mm;
|
|
||||||
}
|
|
||||||
|
|
||||||
#footer {
|
|
||||||
font-size: 95%;
|
|
||||||
padding-top: 10px;
|
|
||||||
}
|
|
||||||
</style>
|
|
||||||
</head>
|
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p>
|
Reports any unresolved references to named patterns ("define") in RELAX-NG files using the XML Syntax.
|
||||||
This inspections checks for any unresolved references to named patterns ("define") in a RELAX-NG file in XML Syntax.
|
For unresolved references, a quick fix is offered to create a corresponding define-element.
|
||||||
For unresolved references, a QuickFix is offered to create a corresponding define-element.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p id="footer">Powered by RELAX-NG Support</p>
|
|
||||||
</body>
|
</body>
|
||||||
</html>
|
</html>
|
||||||
|
|||||||
@@ -1,26 +1,6 @@
|
|||||||
<html>
|
<html>
|
||||||
<head>
|
|
||||||
<style type="text/css">
|
|
||||||
body, table {
|
|
||||||
font-family: Verdana, sans-serif;
|
|
||||||
font-size: 100%;
|
|
||||||
padding-left: 2mm;
|
|
||||||
}
|
|
||||||
|
|
||||||
#footer {
|
|
||||||
font-size: 95%;
|
|
||||||
padding-top: 10px;
|
|
||||||
}
|
|
||||||
</style>
|
|
||||||
</head>
|
|
||||||
|
|
||||||
<body>
|
<body>
|
||||||
<p>
|
Reports unused named patterns ("define") in a RELAX-NG file (XML or Compact Syntax).
|
||||||
This inspections checks for any unused named patterns ("define") in a RELAX-NG file (XML or Compact Syntax) and
|
A define will not be marked as unused if it is used through an include in another file.
|
||||||
highlights them as unused symbols. This is done with respect to includes from other files, i.e. a define is not
|
|
||||||
marked as unused if it is used through an include in another file.
|
|
||||||
</p>
|
|
||||||
|
|
||||||
<p id="footer">Powered by RELAX-NG Support</p>
|
|
||||||
</body>
|
</body>
|
||||||
</html>
|
</html>
|
||||||
|
|||||||
Reference in New Issue
Block a user