Change theme
Help
Press space for more information.
Show links for this issue (Shortcut: i, l)
Copy issue ID
Previous Issue (Shortcut: k)
Next Issue (Shortcut: j)
Sign in to use full features.
Vote: I am impacted
Notification menu
Refresh (Shortcut: Shift+r)
Go home (Shortcut: u)
Pending code changes (auto-populated)
View issue level access limits(Press Alt + Right arrow for more information)
Request for new functionality
View staffing
Description
When using FragmentStrictMode, it might not be possible or prudent to fix all violations at once.
It would be convenient to let developers build up their allow list of Fragment class name + Violation class name pairs that could serve as the baseline for their app.
This would allow developers to enable more strict penalties for new violations while slowly working down the set of known violations, effectively allowing them to stop the bleeding and avoid regressions as new features are developed.