Skip to content

Commit 560a5de

Browse files
authored
Merge pull request #90 from googlesamples/update-docs
Update documentation snapshot.
2 parents bbf7306 + 968b534 commit 560a5de

File tree

246 files changed

+5072
-1421
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

246 files changed

+5072
-1421
lines changed

Diff for: docs/api-guide.html

+1,188-322
Large diffs are not rendered by default.

Diff for: docs/api-guide.md.html

+1
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@
88
(insert api-guide/terminology.md.html here)
99
(insert api-guide/basics.md.html here)
1010
(insert api-guide/example.md.html here)
11+
(insert api-guide/ast-analysis.md.html here)
1112
(insert api-guide/publishing.md.html here)
1213
(insert api-guide/unit-testing.md.html here)
1314
(insert api-guide/test-modes.md.html here)

Diff for: docs/api-guide/annotations.md.html

+3-3
Original file line numberDiff line numberDiff line change
@@ -351,7 +351,7 @@
351351
called for the second `pop` call as well, since it calls a method
352352
inside a `@ThreadSafe` annotation (on the outer class), but the `index`
353353
would be 1. The lint check can check all the annotations earlier than
354-
the one at the index to see if they "counteract" the annotation, which
354+
the one at the index to see if they counteract the annotation, which
355355
of course the `@NotThreadSafe` annotation does.
356356

357357
Lint uses this mechanism for example for the `@CheckResult` annotation,
@@ -375,7 +375,7 @@
375375
found in multiple nested contexts, lint *will* include all the
376376
annotations in the `AnnotationUsageInfo`, but it will not invoke
377377
your callback for any outer occurrences; only the closest one. This
378-
is usually what detectors expect: the innermost one "overrides" the
378+
is usually what detectors expect: the innermost one overrides the
379379
outer ones, so lint omits these to help avoid false positives where
380380
a lint check author forgot to handle and test this scenario. A good
381381
example of this situation is with the `@RequiresApi` annotation; a
@@ -405,7 +405,7 @@
405405
for testing purposes, but you have a concrete subclass where you are
406406
deliberately supporting the operation, not just from tests. If
407407
annotations were always inherited, you would have to create some sort
408-
of annotation to "revert" the semantics, e.g.
408+
of annotation to revert the semantics, e.g.
409409
`@VisibleNotJustForTesting`, which would require a lot of noisy
410410
annotations.
411411

0 commit comments

Comments
 (0)