Update and standardize Javadoc. #1487
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
45ba7b7 to
260baca
Compare
- Use `@link` over `@code` in more places. (I didn't use it for self-links, though, because IntelliJ complains about those.) This came up in cl/764872419. It follows the change in our Java practices some years ago.
- Standardize `FooSubject` Javadoc on "A subject for {@link Foo} values
- Remove quotes around "functional interface" in `ExpectFailure` types. (We already go without in types like [`BinaryPredicate`](https://truth.dev/api/latest/com/google/common/truth/Correspondence.BinaryPredicate.html).)
- Fix at least one typo (in `Subject.java`).
RELNOTES=n/a
PiperOrigin-RevId: 771157858
260baca to
aba48c6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update and standardize Javadoc.
@linkover@codein more places. (I didn't use it for self-links, though, because IntelliJ complains about those.) This came up in cl/764872419. It follows the change in our Java practices some years ago.FooSubjectJavadoc on "A subject for {@link Foo} valuesExpectFailuretypes. (We already go without in types likeBinaryPredicate.)Subject.java).RELNOTES=n/a