Last modified: 2014-05-17 00:12:48 UTC
Both look identical making development on this feature hard. Let's get this JavaScript code consolidated.
Fixing this bug means deciding what we want to do with the random campaign feature. If we're keeping it, we consolidate the code. If we're not keeping it, we ditch the KeepGoingDrawer and let the KeepGoingOverlay remain relatively simple.
Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1762
The random feature came out of the fact the KeepGoingDrawer was a generic reusable component, it seems KeepGoingOverlay is less generic now so that's why it isn't using it. I think regardless of whether we keep the random feature this would be a good exercise for future developments using the keep going overlay (also I think the KeepGoingOverlay name is a bit misleading - KeepGoingOverlayDrawer sounds more descriptive).
KeepGoingDrawer doesn't exist anymore.