One of the more important aspect in react development is making sure that that view itself is not too strongly coupled with data and business logic so that we would be able to easily port our apps to react native in the future. In mantra @arunoda is using react-simple-di to do dependency injection to allow access to the actions by injecting them into the root component. In a similar fashion, would it be a good idea to use compose business logic functions through props into their specific component?
For example: In a login form component, the action defined to handle login and login error would be composed along with the data and it can be access through the props in the login component. Is this a good idea in terms of future proofing or is there a better approach to making sure the business logic isn’t too strongly coupled with the view?