| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
These are just nits since this this CL is just an inlining. Feel free to disregard these!
I'm wondering if it's just worth inlining all other cases where booleanNonNullObservableSupplier (and other temps) are used, since I think it subtracts from readability.
booleanNonNullObservableSupplier1.addSyncObserverAndPostIfNonNull(Looks a bit cluttered without the inlined observer ref and the verbose temp var names. Maybe inline the temp vars? Ignore if this involves some kind of problem with generics that I'm aware of.
// Exclusive Access Manager always follows the fullscreen state. We
// subscribe to the FS state supplier in case when the fullscreen is
// delayed. Thanks to that EAM stat supplier will update on all FS
// enter and exit events.
// Exiting fullscreen should unlock all other locks.Duplicated comment.
// On show snackbar, hide page zoom dialogDuplicated comment.
// Safely call onPreferenceChange only on non-null observers (since tablets
// don't call #initBookmarkBarPrefForUserPrefs).Duplicated comment.
integerNonNullObservableSupplier1.addSyncObserverAndPostIfNonNull(mOnStatusBarColorChanged);Same as previous comment related to clutter!
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
These are just nits since this this CL is just an inlining. Feel free to disregard these!
I'm wondering if it's just worth inlining all other cases where booleanNonNullObservableSupplier (and other temps) are used, since I think it subtracts from readability.
Unresolve.
Fiaz MuhammadThese are just nits since this this CL is just an inlining. Feel free to disregard these!
I'm wondering if it's just worth inlining all other cases where booleanNonNullObservableSupplier (and other temps) are used, since I think it subtracts from readability.
Unresolve.
Done
booleanNonNullObservableSupplier1.addSyncObserverAndPostIfNonNull(Looks a bit cluttered without the inlined observer ref and the verbose temp var names. Maybe inline the temp vars? Ignore if this involves some kind of problem with generics that I'm aware of.
Thanks for catching! I only did spot checks and didn't notice this. Pretty sure this is intelli-j just being silly.
// Exclusive Access Manager always follows the fullscreen state. We
// subscribe to the FS state supplier in case when the fullscreen is
// delayed. Thanks to that EAM stat supplier will update on all FS
// enter and exit events.
// Exiting fullscreen should unlock all other locks.Andrew GrieveDuplicated comment.
Done
// On show snackbar, hide page zoom dialogAndrew GrieveDuplicated comment.
Done
// Safely call onPreferenceChange only on non-null observers (since tablets
// don't call #initBookmarkBarPrefForUserPrefs).Andrew GrieveDuplicated comment.
Done
integerNonNullObservableSupplier1.addSyncObserverAndPostIfNonNull(mOnStatusBarColorChanged);Same as previous comment related to clutter!
Done
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Code-Review | +1 |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |
Inline ObservableSupplier.addObserver() (part 1)
The call is an alias for "addSyncObserverAndPostIfNonNull()".
Used Android Studio to inline the method from
NonNullObserverableSupplier (entirely mechanical).
| Inspect html for hidden footers to help with email filtering. To unsubscribe visit settings. |