Lines Matching refs:it

4 it does not generate docs; it's intended only for **meta**data extraction and
58 Metalava has a new command line syntax, but it also understands the doclava1
84   annotations. This isn't just merged at export time, it's merged at codebase
85   load time such that it can be part of the API analysis.
92   * Improve the signature format such that it for example labels enums "enum"
137   * Misc documentation handling; for example, it attempts to fix sentences that
155   the API and which one is implementation; it is simply handed the filtered API
166   but not versa).  It also lets you diff directly on a source tree; it does not
175   StringBuilder.setLength(int) was missing from the API signatures since it is a
178   anyway since it packages package private classes. Metalava strictly applies
180   hooked up to the build it immediately became apparent that it was missing
187   possible with the signature-file based Python version; for example, it looks
193   finds a problem, it will only be reported if it is not already in the
201   target efforts since we plan to annotate the entire API). First, it can
209   More importantly, you can also point it to some existing compiled applications
210   (.class or .jar files) and it will then measure the annotation coverage of the
214   framework, and pointing it to the
270   From this it's clear that it would be useful to start annotating
277   had to require the constants to all share a single prefix it could look
279   level, so it can resolve references and map them back to the original field
295   android.jar files themselves to ensure that it computes the exact available
334 to a source tree or a .jar file, and it constructs Items built on top of PSI:
339 are hidden, which is why it's called a "Codebase" rather than an "API").
427 This makes it easy to perform API comparison operations.
430 annotations as migrated. To do this, it just extends `ComparisonVisitor`,
442 remove API. (The real check is slightly more complicated; it looks into the
452 Doclava1 was integrated with javadoc directly, so the way it generated metadata
457 This it not how metalava does it; it generates the English documentation
461 generates the documentation is easier to reason about and to update when it's
463 grammar, e.g. when it's listing a number of possible constants the conjunction
464 is usually "or", but if it's a flag, the sentence begins with "a combination of