Hey there, noob question but as a fan of sound terminology I wonder: what is the code-behind-file within the MVVM pattern? The ViewModel? The Model? Or like the css, is it part of the View, i.e. the View consisting of multiple file types?
And why is it called MVVM while in fact the “call chain” is View <-> ViewModel -> Model, so shouldn’t it be V2M2?
And finally, why in the groceries tutorial within playground is the ViewModel a mixup of presentation and business logic? Why not putting us newbies on the right track from the beginning and clearly separating viewmodels and models (or maybe I overlooked it)?