Lines Matching refs:it

3 (Also known as "doclava2", but deliberately not named doclava2 since crucially it
4 does not generate docs; it's intended only for **meta**data extraction and generation.)
53 Metalava has a new command line syntax, but it also understands the doclava1
81   annotations. This isn't just merged at export time, it's merged at codebase
82   load time such that it can be part of the API analysis.
89   * Improve the signature format such that it for example labels enums "enum"
135   * Misc documentation handling; for example, it attempts to fix sentences
154   implementation; it is simply handed the filtered API stub sources that include
165   but not versa).  It also lets you diff directly on a source tree; it does not
174   StringBuilder.setLength(int) was missing from the API signatures since it is
177   anyway since it packages package private classes. Metalava strictly applies
179   hooked up to the build it immediately became apparent that it was missing
183   target efforts since we plan to annotate the entire API). First, it can
191   More importantly, you can also point it to some existing compiled applications
192   (.class or .jar files) and it will then measure the annotation coverage of
196   version of framework, and pointing it to the
251   From this it's clear that it would be useful to start annotating android.os.Parcel
258   constants to all share a single prefix it could look for. However, in metalava,
259   annotation references are available at the AST level, so it can resolve references
274   it computes the exact available SDK data for each API level.)
306 source tree or a .jar file, and it constructs Items built on top of PSI:
311 that are hidden, which is why it's called a "Codebase" rather than an "API").
400 This makes it easy to perform API comparison operations.
403 as migrated. To do this, it just extends `ComparisonVisitor`, overrides the
415 remove API. (The real check is slightly more complicated; it looks into the
425 Doclava1 was integrated with javadoc directly, so the way it generated
430 This it not how metalava does it; it generates the English documentation
435 update when it's handling loop conditionals. (As a result I for example
436 improved some of the grammar, e.g. when it's listing a number of possible
437 constants the conjunction is usually "or", but if it's a flag, the sentence
448 - the code needs cleanup, and some performance optimizations (it's about 3x