Once we have a controlled form set up in React, we have to handle getting that data from the form and to the appropriate location to update state, so that the new information can be rendered to the DOM. Inverse data flow is a key part of making that happen.
Controlled forms are an important part of writing code when using React. So I read. Many times in the React docs. It wasn’t until my instructor gave a rather silly example that all the pieces of a controlled form clicked for me.
Just today I wrapped up my fourth project for flatiron using Ruby on Rails as an API for the backend and with a vanilla JavaScript frontend. Witchy Wardrobe is a closet organising SPA that allows you to create items of clothing and outfits. It is intended to help people realise how much they spend on clothes, how often do they use clothing items, and create outfits. It would be a great supplemental tool for someone trying out Project 333, the 4x4 capsule, or any other minimalist closet.
Just today I wrapped up my third project for flatiron using Ruby on Rails. I enjoy reading and so decided to create the “Book Nook”, a website that allows users to add books to the Book Nook’s collection, create reading lists and add books to their lists, and also write reviews of books. The website also keeps track of the top five reviewers and the top ten highest ranked books based on their average rating. It has typical sign up, login, and logout functionality plus the additional option to sign up/login using a Github account through Ominauth.
The past two weeks have been spent working on my second project for Flatiron’s Software Engineering Bootcamp. It is an MVC app built using Sinatra. For my project I decided to create a recipe catalog that would allow a user to make recipes to save in their catalog, and provide them the option to view all of their recipes in a list or organised by category. This was mostly selfishly motivated as I have recipes written on notecards, in three different notebooks, and scraps of paper stuck to the refrigerator.