Skip to content

Releases: Arello-Mobile/Moxy

v1.5.3

14 Jun 08:35
Compare
Choose a tag to compare
  • Allow to specify MoxyReflector package and use it from another module (pull request)

v1.5.2

14 Jun 08:34
Compare
Choose a tag to compare
  • Optimize memory usages, when View detach from presenter but still alive

v1.5.1

14 Apr 07:36
Compare
Choose a tag to compare
  • Fixed bug of save Android view state (issue 114)

1.5.0

13 Apr 13:32
Compare
Choose a tag to compare
  • Fixed leak of presenters when it's in child delegate
  • Annotation processor enchxansement

v1.4.6

10 Mar 11:01
Compare
Choose a tag to compare
  • Improve support of generics
  • Fix crash when no usages of Moxy's annotations
  • Fix call of MvpDelegate's methods in Fragment

v1.4.5

16 Jan 06:32
Compare
Choose a tag to compare
  • Change callbacks execute time
  • Doesn't call presenter.detachView(view) if this view has been detached

v1.4.4

10 Jan 11:05
Compare
Choose a tag to compare
  • Added javadoc and sources

v1.4.3

29 Dec 19:36
Compare
Choose a tag to compare
  • Removed reflection
  • Added some tests

v1.3.3

07 Dec 09:58
Compare
Choose a tag to compare
  • Fixed a potential NullPointerException
  • Fixed moment of execute some MvpDelegate methods

v1.3.2

29 Nov 14:26
Compare
Choose a tag to compare
  • Fixed MvpFragment/MvpAppCompatFragment lifecycle callbacks
  • MvpView will be detached from Presenter:
    • inside onSaveInstanceState, if it will be called. You be able to not commit fragments transaction allowing state loss! Just use commit or commitNow ! If you don't use Cicerone.
    • inside onStop otherwise
    • after MvpView will be restarted, it will apply only new commands!
    • after MvpView will be recreated, it will apply all commands.
  • Added OneExecutionStateStrategy
  • Small changes (like javadocs)

PS: Added MvpDelegate.onDestroyView() which should be called when view will be destroyed. Causes of this is that detached view can stay alive. Example of use this beyond of Fragment is there.