IssueTracker

Component used: Fragment Version used: 1.4.0-alpha01

Each instance of androidx.fragment.strictmode.Violation tracks a specific type of StrictMode violation. Ideally, each subclass of Violation should have enough structured information (i.e., getters) to allow developers to verify exactly what caused the violation. This could include the Fragment instance itself or violation specific information. This would greatly improve the ability to have custom loggers extract this information and parse it in a useful way.

The base Violation class should have a getFragment() method that returns a NonNull Fragment instance that caused the Violation.

Examples of information I'd expect to be available:

• FragmentReuseViolation:
  • The unique ID of the previous instance (this may require replacing the private mRemoved flag with a mPreviousWho nullable String).
• FragmentTagUsageViolation:
  • The parent ViewGroup that the Fragment would have been added to.
• RetainInstanceUsageViolation:
  • This should be split into two subclasses of RetainInstanceUsageViolation: SetRetainInstanceUsageViolation and GetRetainInstanceUsageViolation to allow distinguishing the two cases
• SetUserVisibleHintViolation:
  • a boolean indicating on whether the fragment was being set isVisibleToUser or not
• TargetFragmentUsageViolation
  • This should be separated to subclasses of TargetFragmentUsageViolation:
    • SetTargetFragmentUsageViolation would include the target Fragment instance and the int requestCode
    • GetTargetFragmentUsageViolation (no additional information)
    • GetTargetFragmentRequestCodeUsageViolation (no additional information)
• WrongFragmentContainerViolation
  • The ViewGroup container that the Fragment was trying to be added to