Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Why are presenters injected to activities and not to fragments?
See original GitHub issueIs there any benefit of injecting the presenters in Activities rather than in Fragments? The Activities do nothing but attach the Fragment which handles all the user interactions using the Presenter.
Take AddEditTaskActivity as an example. As the presenter is injected in it’s onCreate() method, the presenter will be recreated during orientation changes. However if the presenter was injected into the AddEditTaskFragment it would have been retained through orientation changes too. This can be particularly useful in case the presenter has to maintain any state.
Just want to know what everyone thinks about this approach?
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:7 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@JoseAlcerreca How can we use the same presenter on 2 fragments within the same activity? Don’t you think we should have a sample of that since I think most devs use multiple fragments in the same activity.
I use it in Fragment. But I find Presenter will be NULL when I recycle my memory.