Squash Tomato Journal — November 15, 2017–00:00
Published in
1 min readNov 16, 2017
- Began writing a blog post on how to use Socket.io in a MVC app.
- Worked with a few friends who had experience with WebSockets.
- Started to realize that my backend logic for Squash Tomato wouldn’t be able to handle the features I wanted to build, so I’m rewriting my backend logic and I’ll make it public (you’re going to see quite a bit in this post).
- I’m making a document that contains all the details of my app including what X is for and why X is the way it is. The details and flow of my app was becoming a bit much to continue to manipulate and maintain as a mental image, so I’m organizing by getting it into documentation.
- I found 5 major areas/things needing refactor before I launch my big Family List update — the User model list data needs moved into a new List model (involves changing all of my controller JavaScript to work with a different model), all list relationships of a single user should be displayed in a new /my-lists page, all lists are shareable AND deletable, client-side JavaScript should contain only pure functions to improve reusability and prevent unintended bugs, and client-side JavaScript should work with any list regardless of how many members have access and “write” permissions.
- Looking for a way to move a field from my User model into new documents within a new collection of my new List model… sigh.
