Context: Ok, so I’m doing a little recipe management system for a project. I know, everyone has done this a thousand times. I’m hoping to take mine to a bit of higher lever, though. I used to manage kitchens and even worked as a sous chef, so the end goal is to have a basic kitchen supply management system that I can use not just to store recipes, but also to track the raw cost of ingredients and recipes as well as generate weekly menus and grocery lists. As I develop this application, I’ll put the subsequent blog posts right here:
previous blog post: https://etcusic.github.io/single_page_javascript_app_using_object_orientation github repo: https://github.com/etcusic/memory-game-interface
As of writing this my application is still pretty small, so incorporating Redux felt a bit less intuitive. After getting the hang of using the Redux store, though, I certainly understand how having it to manage global state can be super helpful as I grow an application. The setup was a bit trickier than I was anticipating, so I figured I’d document the bare bones of its setup for future reference.
Context: The challenge for this project is to make a dynamic single (HTML) page web application using vanilla JavaScript to manipulate the DOM and a Rails API server to fetch requests from.
Context: For this project we need to have a many-to-many relationship with a has_many through relationship. I decided to do an application in which tutors can have many students through appointments and vice versa. With both tutors and students being a type of user I had a decision to make about how I wanted to set up the tables and classes in order to have the cleanest/clearest setup possible for my relationships. For a base user model, I wanted there to be a name, email, and password_digest, and then tutors & students would have several of their own unique attributes ascribed to their models. There are a number of ways to set this up as models and tables, so I had to sort through them to find the clearest and DRYest way possible.