- 20ab154 Document AutoBuilder. by Éamonn McManus · 3 years, 3 months ago
- 89c0e53 Sync "How do I..." between builders.md and builders-howto.md. by Michał Sobkiewicz · 3 years, 4 months ago
- 6fc8074 Suggest `compileOnlyApi` rather than `compile` for AutoValue with Gradle. by Éamonn McManus · 3 years, 5 months ago
- 984e893 Document how to create a "step builder" with AutoValue. by Éamonn McManus · 3 years, 5 months ago
- 2f1cef9 Add spacing after the simple name when generating a `@ToPrettyString` representation. by Ron Shapiro · 3 years, 5 months ago
- 8906740 Add documentation for `@ToPrettyString` by Ron Shapiro · 3 years, 5 months ago
- 8e5f765 Add some clarifications on the implicit default value for "AutoValue collection property". by Google Java Core Libraries · 3 years, 5 months ago
- f19117a Allow an AutoValue property builder to have a parameter. by Pawel Labaj · 3 years, 5 months ago
- 75c5d95 Strip the whole "More information" section; there is no sidebar/top-left on GitHub where this appears. by Colin Decker · 3 years, 7 months ago
- dbb398b Adjust IgnoreExample of AutoValue doc for thread safety by Google Java Core Libraries · 3 years, 7 months ago
- 47fc7b9 Automatic code cleanup. by Google Java Core Libraries · 4 years ago
- 43ff5f2 AutoValue annotation can be provided scope. by rayt · 4 years, 1 month ago
- 08f930a Make the nested @AutoValue class static otherwise you get the following error: by nnegrey · 4 years, 2 months ago
- 32fdb09 Change links from google.github.io/guava to guava.dev, including making sure they're https. by cpovirk · 4 years, 2 months ago
- b22f969 Copy annotations from `@AutoValue.Builder` to the generated `Builder` subclass. by emcmanus · 4 years, 2 months ago
- 365d3f6 Demonstrate a static copy function instead of .clone() by diamondm · 4 years, 3 months ago
- 6aeb44f Generalize the logic for determining if we can make a BarBuilder out of a Bar. by emcmanus · 4 years, 3 months ago
- e4ab0e7 Fix broken link in howto.md by cpovirk · 4 years, 4 months ago
- 36a53b9 Minor reformatting of markdown by cpovirk · 4 years, 5 months ago
- 8b17dd8 AutoValue best practices: mention that subclassing is now prevented. by ghm · 4 years, 7 months ago
- 4a8736f Suggest calling out a misuse in AutoValue regarding @Nullable fields. by yunqin · 4 years, 8 months ago
- b319597 Improve Maven instructions for AutoValue. by emcmanus · 4 years, 8 months ago
- ab2f067 Be more explicit about which Java versions AutoValue supports. The compiler must be at least Java 8, but it can generate code for Java 7. by emcmanus · 4 years, 9 months ago
- 7dc5450 Document that <annotationProcessorPaths> is the preferred way to use auto-value for Maven and Gradle. by dpb · 4 years, 10 months ago
- 2038f34 Try to explain better what happens to callers when you offer both set-at-once and gimme-a-builder methods. by kevinb · 4 years, 10 months ago
- 45c55bd Grammar correction by nitinsurana · 5 years ago
- 0bc8a2e Update the AutoValue release mentioned in the docs from 1.6.5 to 1.6.6. by emcmanus · 5 years ago
- 4e3366b Update live version of auto-value from 1.6.2 to 1.6.5 by glorioso · 5 years ago
- 395c08f Clarify the FAQ on interfaces. by jasonmbaker · 5 years ago
- 91118b0 Document the order of properties in @AutoValue classes. This matters when a class inherits abstract methods from more than one place and uses a constructor rather than a builder. by emcmanus · 5 years ago
- 63f2276 add details for how to write the AutoValue class when it is an inner class by alikh · 5 years ago
- 48d6557 Allow @AutoOneOf properties to be void. by emcmanus · 5 years ago
- a81a9e2 Add sentence to AutoValue user guide to explain where the order of the constructor parameters comes from. by nhcohen · 5 years ago
- 36ccd0f Document re-abstracting concrete methods more explicitly, including the case of default methods in interfaces. by emcmanus · 5 years ago
- b6dcc5e Adding call out to naming for builders in autovalue by cast · 6 years ago
- 43321e9 Update docs for 1.6.2. by cpovirk · 6 years ago
- 96370f3 Add capability to annotate individual AutoValue fields by croyer · 6 years ago
- 0ffe45c Replace http://errorprone.info with https://errorprone.info since that site by glorioso · 6 years ago
- 98385e3 Remove text about `apt` configuration with Gradle annotation-processing plugin. by emcmanus · 6 years ago
- 83e8094 Update AutoValue's Gradle documentation to account for the built-in annotation processor configuration. by jakew · 6 years ago
- dabf8ed Update index.md to explain 1.6 configuration, now that 1.6 has been released. by emcmanus · 6 years ago
- f25bf7e Document @AutoOneOf in the AutoValue user guide. by emcmanus · 6 years ago
- 56bff25 Some markdown fixes by emcmanus · 6 years ago
- 2b88377 Revert changes to AutoValue documentation that talk about 1.6, until we can actually release 1.6. by emcmanus · 6 years ago
- 04d00ca Remove stray empty file by danielmoy · 6 years ago
- 0c488d7 Create an auto-value-annotations artifact separate from the processor by ronshapiro · 6 years ago
- 4add4c7 Show an example of providing both forms of setter for an Optional property. by hfiller · 7 years ago
- 3245925 Update the example generated code for builders to reflect the current generator. by emcmanus · 7 years ago
- 021bf05 Clarify why mutable fields shouldn't be used in AutoValue classes. by johnerez · 7 years ago
- 8872153 Bump maven/gradle instructions to use current release. by emcmanus · 7 years ago
- ce59a6c Add troubleshooting to markdown for two equal AutoValue objects not evaluating as equal. by fudgee · 7 years ago
- ed79984 Mention semantics of concurrent calls to @Memoized methods. by diamondm · 7 years ago
- 12599fd Avoid trying to show an iframe in github markdown. It doesn't work there. by Ahmad El-Melegy · 7 years ago
- 4168818 Clarify an Effective Java reference in the AutoValue documentation. by Clinton Curry · 7 years ago
- e235e08 Change markdown links so they no longer have a line break between ] and (. Github recently stopped recognizing links like this, and pointed out <https://github.com/github/markup/issues/1026> that they are not covered by the Commonmark spec. by emcmanus · 7 years ago
- eb773de Update AutoValue CHANGES.md with the 1.3 → 1.4 changes. by emcmanus · 7 years ago
- 4a66e02 very minor edit by kevinb · 7 years ago
- d71ec14 Internal bookkeeping. by emcmanus · 7 years ago
- 9a39dfe Automated g4 rollback of changelist 145718483. by emcmanus · 7 years ago
- 8e813e4 Internal bookkeeping. by suzhang · 8 years ago
- 013ee50 Sync with latest Google changes. by kevinb · 8 years ago
- 3befbdc Revisions to @Memoized content and warning that ignoring fields in eq/hc might not be what you really want. by kevinb · 7 years ago
- 6d51525 Document the new "generalized property builders" feature for @AutoValue. by emcmanus · 8 years ago
- 3dc3dde Strip incompatible id. by dpb · 8 years ago
- 52e2335 Beginning of Extension docs by dpb · 8 years ago
- 15057a1 Add @Memoized to the open-source AutoValue project. by dpb · 8 years ago
- ec78694 Fix typo by marslan · 8 years ago
- 4571d1e Make AutoValue.Builder examples use "set" prefixes, which makes them easier for readers to understand, and I believe is generally more common in the wild for builders, EJ notwithstanding. by kevinb · 8 years ago
- 5ec14eb Add @Memoized docs to [] (unpublished). by dpb · 8 years ago
- 88c0485 Fix typo noted by ersin-ertan in https://github.com/google/auto/pull/351. by emcmanus · 8 years ago
- a304a6f Copy (and modify) the dagger release docs over to auto-value so they can be used in releasing that product. by cgruber · 8 years ago
- ef9c37a Clarify documentation about annotating AutoValue fields. by nwatson · 8 years ago
- 7de1915 Add support for "optional getters", where a getter in an AutoValue Builder can have type Optional<T> and it will return Optional.of(x) where x is the value that has been set in the Builder, or Optional.empty() if no value has been set. by emcmanus · 8 years ago
- c80e131 Document the new special support for Optional in AutoValue builders. by emcmanus · 8 years ago
- 0ef134d Update to Guava 19 by ronshapiro · 8 years ago
- 10da295 Changing concrete methods to final so that the example code follows best practices: [] by okeskin · 8 years ago
- 1639603 Bump documentation to auto-value-1.2, add (tested) gradle instructions, and tidy up the README source a bit. by cgruber · 8 years ago
- 8468735 Shrink README.md to a very small document that points to the full documentation in userguide/index.md. Also, change the version number in the pom.xml excerpt in userguide/index.md. We changed this in README.md but not there. by emcmanus · 8 years ago
- 2c9920f Remove {#link} anchors, which do not work with github's markdown. by emcmanus · 8 years ago
- e617667 Make the comment for nested class use less ambiguous, to indicate the name of the outer class should be used, not the string "Outer" by levik · 8 years ago
- 6d3ecf1 Add example of making some params nullable. by azlatin · 9 years ago
- 1ce34b6 Publish the hitherto internal AutoValue guide as value/userguide. by emcmanus · 9 years ago