IssueTracker

The @setparam: use-site target annotation is meant to annotate a property with an annotation that is meant to be added to the parameter of the generated setter.

However, this does not seem to be correctly handle by Metalava, which does not include the annotation in the generated API file.

See aosp/1690007 for one such example where I replaced a manually configured getter and setter:

    @Px
    public var chinHeight: Int = 0
        @Px get
        set(@Px value) {
            field = value
        }

with the equivalent (and more compact):

    @Px
    @get:Px
    @setparam:Px
    public var chinHeight: Int = 0

which requires an updated API file which removes the parameter annotation.

Note that the generated code seems to be identical for these two versions:

$ javap -v -cp x/classes.jar androidx.wear.watchface.MutableWatchState
[...]

  public final void setChinHeight(int);
    descriptor: (I)V
    flags: (0x0011) ACC_PUBLIC, ACC_FINAL
    Code:
      stack=2, locals=2, args_size=2
         0: aload_0
         1: iload_1
         2: putfield      #74                 // Field chinHeight:I
         5: return
      LineNumberTable:
        line 104: 0
        line 105: 5
      LocalVariableTable:
        Start  Length  Slot  Name   Signature
            0       6     0  this   Landroidx/wear/watchface/MutableWatchState;
            0       6     1 value   I
    RuntimeInvisibleParameterAnnotations:
      parameter 0:
        0: #70()
          androidx.annotation.Px
[...]