Releases: google/auto
Releases Β· google/auto
AutoFactory 1.1.0
- AutoFactory now recognizes and generates both
javax.inject
andjakarta.inject
. Ifjakarta.inject
is on the classpath then it will be used, and otherwisejavax.inject
. A new compiler option-Acom.google.auto.factory.InjectApi
can be set to eitherjavax
orjakarta
to force the use of one or the other. (67772b2) - There is now a way to add annotations to generated AutoFactory classes. See the javadoc for
@AutoFactory.AnnotationsToApply
. (b2a1c08) - The exception message for a null value now indicates not only which number argument it is but also how many arguments there are in total. This may lead to a small increase in code size. (ab6c7bf)
- AutoFactory now correctly handles the case where a parameter annotation has
@Target
with bothPARAMETER
andTYPE_USE
. (9d455fa) - When a requested supertype of the generated factory class has a type parameter, the generated class now always has the same parameter. (206b673)
- Better error message when detecting duplicate parameters (59ec5e6)
AutoValue 1.10.4
- A workaround for a JDK bug with reading jar resources has been extended so it always applies, rather than just as a fallback. See #1572. (3f69cd2)
- If an AutoValue property method is
@Nullable
, the corresponding field in the generated class will be too. This was already the case forTYPE_USE
@Nullable
or if the method had@CopyAnnotations
, but now@Nullable
will be copied in other cases too. (4506804)
AutoValue 1.10.3
AutoValue 1.10.2
- The constructor parameter names in the class generated by
@Memoized
no longer add a$
. This may require changes to code that was depending on the old names, for example using Error Prone's/* param= */
comments. (4f8dbea) - An AutoValue or AutoBuilder property is now allowed to be null if its type is a type variable with a
@Nullable
bound, like<T extends @Nullable Object>
. (1b58cff) - Better error message when AutoValue, AutoBuilder, etc give up because of missing types. We now say what the first missing type was. (2e734f6)
- AutoBuilder copy-constructors no longer require an exact match between a property and the corresponding constructor parameter. (1440a25)
- A property of type
List<T>
can be built by a property builder whosebuild()
method returnsList<? extends T>
. (8ba4531) - Made it easier to support
@CopyAnnotations
in AutoValue extensions, via new methodsclassAnnotationsToCopy
andmethodAnnotationsToCopy
. (a3f218d) - Generated builders now include a
@Nullable
type annotation on appropriate builder fields if one is available. (91d5f32) - Updated
@AutoAnnotation
documentation to say that it isn't needed in Kotlin. (600b4b6) - Maven dependencies have been updated, fixing #1532.
auto-service-1.1.1
What's Changed
- No functional changes.
- Dependencies updated.
- Some minor code improvements.
Full Changelog: auto-service-1.1.0...auto-service-1.1.1
auto-common-1.2.2
What's Changed
- No functional changes.
- Dependencies updated.
Full Changelog: auto-common-1.2.1...auto-common-1.2.2
AutoService 1.1.0
- AutoService now verifies by default that the annotated class does indeed implement the interface in
@AutoServce
. Previously this only happened when compiling with-Averify=true
. The verification can be disabled either by compiling with-Averify=false
or by adding@SuppressWarnings("AutoService")
to the annotated class. (965e893) - The
@AutoService
annotation can no longer be applied to an interface or abstract class. This new verification can also be disabled in the same way. (591731c)
AutoService 1.0.2
Updating Maven dependencies only. No functional changes.
AutoValue 1.10.1
AutoValue 1.10
- AutoBuilder is now stable and supported. (2e44a53)
- AutoBuilder now allows you to omit a Kotlin default parameter when building a Kotlin class. (d2f91bf)
- An
@AutoBuilder
class can now have@AutoValue.CopyAnnotations
so annotations are copied from the class to its generated subclass. (3a15c88) - The generated AutoBuilder class now has a "copy constructor" if values for the builder properties can be obtained from the built type. (b3b53a3)
- AutoBuilder can now be used to build annotation implementations directly. (196c810)
- Fixed an issue when Serializable and Memoized extensions are used together. (e01968d)
@AutoAnnotation
now hasCLASS
rather thanSOURCE
retention, making for better operation with Gradle incremental compilation. (34c3be5)@AutoAnnotation
methods no longer need to be static. This makes it easier to use AutoAnnotation with Kotlin. (cf55dc6)- AutoValue and AutoBuilder builders now use bitmasks to track unset primitive properties, which will typically lead to smaller builder objects and faster build times. (b5d3989)