IssueTracker

If a Kotlin property is defined with an explicit setter which has as a parameter name something other than the exact name of the property, that parameter name is ignored in the generated Java docs, and the property name is used instead. This is maybe an upstream issue.

For example, the following definition:

class Foo {
  var currentState: Int
    get() = 0
    /**
     * Sets the state.
     * @param state new state
     */
    set(state) {}
}

setCurrentState will appear in the Java docs with a param named currentState, even though it has been named state in the code. (this makes the @param state problematic)

(Though if this is fixed it will cause an error for any existing cases when an overriden property explicitly defines a setter with a differently named parameter but the parent does not. This is the case for LifecycleRegistry.currentState, parent Lifecycle.currentState.)