TheSwiftDojoDo you layer UI patterns on top of #SwiftUI patterns making a house of cards?
Apple doesn’t profess to dictate UI patterns but … there are inherent patterns at work.
camsoft2000@TheSwiftDojo I’m interested in this as someone who has heavily invested in MVVM and SwiftUI. While I appreciate the Action, State, View loop you mention, this is still the same loop when using MVVM, action, updates model (state), view updated. That said I do find that using MVVM feels like it’s fighting the default architecture patterns. Just wish Apple had codified the Swift UI architecture pattern to avoid this mess. We use MVVM to encapsulate business logic and view logic, also aid testing.
@camsoft2000 Do you experience the Preview as a test?
I have switched my thinking about TDD and Preview as a First Class Test.
It's the first test I write and the test that runs most frequently & is consistantly annalysied & optimized easly.
@TheSwiftDojo Can you explain what you mean by Preview as a test? I agree manual testing is just as powerful as TDD but for me the real value of tests is protecting against regressions and giving confidence to enable future refactoring.
@camsoft2000 defining test is a tricky business - I did years ago let me look it up.
@camsoft2000 regression testing is an interesting practice because it means that someone makes a conscious change that results in an nonobvious breakage of previous working code. That is a long chain of causal links.
I feel the whole ball of reasoning convoluted and predicated on the nonobvious (nonsensical) which a good/great/competent dev is tricked by the code into making a mistake. Rather that hoping a test catches it - why not work to make the mistake obvious?
@camsoft2000 humans are capable of making many many almost instant judgements about such things as” looks good” - why not use that superpower ?