level which can used to give the city's name , but that api requires an api key from google cloud
private fun updateUser() {
val newUser = User(
id = editProfileViewModel.getId(),
firstName = rootView.firstName.text.toString(),
lastName = rootView.lastName.text.toString(),
details = rootView.details.text.toString(),
facebookUrl = rootView.facebook.text.toString().emptyToNull(),
twitterUrl = rootView.twitter.text.toString().emptyToNull(),
contact = rootView.phone.text.toString().emptyToNull()
)
editProfileViewModel.updateProfile(newUser)
}User has the property of instagramUrl
by viewModel<AViewModel>() and parameterOf(this) to work in Dagger
easiest solution may not be the best
Unless it effects performance, maintainence or user experience, easiest solution is quite literally the best. The less lines of code you have to write, less you have to maintain and less you have to fix bugs in. The only drawback of Koin is that you have to register every injectable as it is actually a service locator. Dagger - 1 Koin - 5
We have a test to check everything is injectable - great work, I'd love to look into them. better to invest time in writing tests
in Koin we are doing like ViewModel injection and assisted inject which require PhD in Thermosiphon to be done in Dagger. - solutions are already made.
Unless it effects performance,- service locators will affect performance from my knowledge, not sure how much. please explain if you know
service locators will affect performance from my knowledge, not sure how much
As much as using a map vs a getter to get a property. If you are injecting viewmodels in Dagger, then you are using a Map anyway which is most of our injections anyway
@Inject annotation
The complete schedule of the event is here: https://summit.fossasia.org/event/schedule.html
@/all Love #webdevelopment #Python #Javascript? Become a web developer and work on the #openevent software powering
eventyay.com. Convince us to hire you by making a pull request! More info on https://jobs.fossasia.org
