IssueTracker

• Component used: Fragment
• Version used: 1.3.0-rc01
• Devices/Android versions reproduced on: irrelevant

The documentation of Fragment.setFragmentResult extension function of fragment-ktx is wrong about nullability of result.

/**
 * Sets the given result for the [requestKey]. This result will be delivered to a
 * [FragmentResultListener] that is called given to [setFragmentResultListener] with the same
 * [requestKey]. If no [FragmentResultListener] with the same key is set or the Lifecycle
 * associated with the listener is not at least [androidx.lifecycle.Lifecycle.State.STARTED], the
 * result is stored until one becomes available, or [clearFragmentResult] is called with the same
 * requestKey.
 *
 * @param requestKey key used to identify the result
 * @param result the result to be passed to another fragment or `null` if you want to
 *               clear out any pending result.
 */
public fun Fragment.setFragmentResult(requestKey: String, result: Bundle) {
    parentFragmentManager.setFragmentResult(requestKey, result)
}

@param result the result to be passed to another fragment or null if you want to clear out any pending result.

result is annotated @NonNull on FragmentManager Java API and the Kotlin type of result is Bundle, not Bundle?.

How can we "clear out any pending result" then?

Related to this, how should we communicate "cancel" or "no result" with this API? An empty bundle?