Fernando Cejas

Sorry for the late reply guys but I'm with @caseykulm a priori. Although @misrakli can you give us an specific example of what you are trying to do?

@misrakli I do not see any problem here. The repository in the data layer executes the operation atomically and just in case it fails, you could throw an exception and...

So in that case, buildUserCaseObservable is no longer useful and you will have to pass them via setter (with defensive code and failing fast in case all the dynamic parameters...

I re-opened this since it was a pending task and due to the lack of time I could not do it. Thanks for all the input/feedback, here is the commit...

I also wrote an article with the arguments behind the design decisions: http://fernandocejas.com/2016/12/24/clean-architecture-dynamic-parameters-in-use-cases/ As usual, any feedback is very welcome. Merry Christmas! 😄 🎄

@Dharmendra10 We know there are no silver bullets and sharing experiences is awesome. Thanks

Sorry for the late reply but I will take all this feedback for the next version of frodo.

I get your idea. Have you considered to implement it and send a PR? Thanks so much.

@spirosoik sorry for the late reply. Good feedback to keep an eye on for the next version of frodo :)

@tieorange This is not going to be implemented, unless you send a PR 👍 There are efforts from my side to work on Frodo 2: https://github.com/android10/frodo2