Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Where should the data model for sending between activity/fragment stay. #56

Open
arohim opened this issue Mar 19, 2019 · 2 comments
Open

Comments

@arohim
Copy link

arohim commented Mar 19, 2019

I have a question
the data model that are using for sending between activity/fragment live?

the data model most likely domain's data model but it's can be serialized/Parcelized

@arohim arohim changed the title Where the data model for sending between activity/fragment stay. Where should the data model for sending between activity/fragment stay. Mar 19, 2019
@piotrek1543
Copy link

Sorry for late answer... I assume that you're talking about parcelable/serializable model objects which you will use only to transfer data between activities/fragments. As they contains limited data which won't be used to update/save model locally/remotely (so it is related only to presentation layer) I would add this there (I mean: in presentation module).

Think also about reusing once created viewModel which would have original data and which could be shared between fragments or activities (dependency injection thing ;-) ).

@arohim
Copy link
Author

arohim commented Jun 11, 2019

Ok, thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants