Compiler Warnings as Errors - WordPress Module - TargetFragment

[ParaskP7]

Parent #17173

This issue is about resolving the getTargetFragment() and setTargetFragment(...) compile warnings for the WordPress module, and possibly, for the lib modules as well.

PS: Some of those warnings are already deprecated (see here).

---

• Instead of using a target fragment to pass results, the fragment requesting a result should use FragmentManager.setFragmentResultListener (String, LifecycleOwner, FragmentResultListener) to register a
  FragmentResultListener with a requestKey using its parent fragment manager. The fragment delivering a result should then call FragmentManager.setFragmentResult(String, Bundle) using the same requestKey. Consider using setArguments to pass the requestKey if you need to support dynamic request keys.
• Instead of using a target fragment to pass results, use FragmentManager.setFragmentResult(String, Bundle) to deliver results to FragmentResultListener instances registered by other fragments via FragmentManager.setFragmentResultListener(String, LifecycleOwner, FragmentResultListener).

---

For more info see:

• Fragment.setTargetFragment
• Fragment.getTargetFragment

[peril-wordpress-mobile]

	Fails
🚫	Please add a type label to this issue. e.g. '[Type] Enhancement'

Generated by 🚫 dangerJS