SPA's are apps too. And as such when creating a SPA you will find yourself writing code to get data, push data, handle validation, change tracking, storing data locally, presenting data, and so much more. All of these roles could be written in a scattered manner across the app, but that causes redundancy, low code re-use and a readability and maintenance headache. And for you pattern folks (like me) it also violates DRY and SRP. So what do we do? Make more, smaller code files that each handle one specific job. You can get the details on how I use this approach in my upcoming Pluralsight course titled "Building Single Page Apps (SPA) with HTML5, ASP.NET Web API, Knockout and jQuery". It's T-minus 2 weeks before it's due to be completed . so it's getting close! You can catch up on the previous ...
Go to the complete details ...