Conversation

Replying to
One think I have been loving is being able to define the abstract class and implementation separately. πŸ› οΈ I also have been putting test files next to source in the lib folder. πŸ€“
1
2
The fact that I can have compile time errors is huge and now want to make them for more things like view models. I have resisted a MVVM style for a long time but I think that there is valid use cases for it. Like being able to update the ui without changing any logic.
1
2
I keep finding myself spending to much time refactoring code based on frameworks, but really working to decouple. Ideally the view is an implementation detail and if I wanted to reuse the dart logic for a CLI app or html then it should be easy to connect.
1
3
Another nice thing about the abstract class + implementation approach is being able to use the import assertions to load the IO or HTML based version at runtime.
4
Show replies