| commit | 70a8bb40935a6816a147aa283b4fb131de984e71 | |
| author | Mugurell <petrumugurel@gmail.com> | |
| Mon, 26 Aug 2019 15:18:33 +0000 (26 18:18 +0300) | ||
| committer | Jeff Boek <jeff@jeffboek.com> | |
| Fri, 30 Aug 2019 01:12:50 +0000 (29 18:12 -0700) | ||
| tree | 81eada9dc8d101abf00fdb5b8d6609b20eff44c8 | treesnapshot (tar.gz zip) |
| parent | aded4479be4c858d7ec2ba9d98147958aef74011 | commitdiff |
[fenix] For https://github.com/mozilla-mobile/fenix/issues/4007 - ShareFragment will set the contained Views' state
ShareFragment which acts as a container would contain all business logic needed
for populating it's Views.
Data initialization should be done only once since the app state has no reason
to change after the ShareFragment is created and is done as soon as possible,
in onAttach().
Because of the expected short lifespan of this fragment, given the fact that
the state has no reason to change and we handle orientation changes ourselves
to keep things simple I didn't use a ViewModel to persist the state.
ShareFragment which acts as a container would contain all business logic needed
for populating it's Views.
Data initialization should be done only once since the app state has no reason
to change after the ShareFragment is created and is done as soon as possible,
in onAttach().
Because of the expected short lifespan of this fragment, given the fact that
the state has no reason to change and we handle orientation changes ourselves
to keep things simple I didn't use a ViewModel to persist the state.