eogas / caloriestack-full-framework

A minimal calorie counting web application

Hi there 👋

My name is Evan and I’m a software developer. I currently live and work (remote) in Milwaukee, WI. I enjoy playing first-person shooters, riding bikes, and analog photography.

• 📘 I’m currently reading Palo Alto by Malcolm Harris
• 🌱 I’m currently learning about Microservices in .NET
• 📫 How to reach me: @eogas
• 😄 Pronouns: He/Him

Buy my mixtape at evanisgreat.com

caloriestack-full-framework's Issues

Verify datepicker functionality

Prerequisite: Need to get creation of days working.

Index page shows horizontal scrollbar all the time

Bookmark reminders

This will require a change in the data model. This is a good opportunity to work on getting db migrations working correctly.

Figure out hosting

Probably just put it on azurewebsites.com for the first version. Eventually we want to change caloriestack.evanogas.com to point to hosted instance.

Stack cookie

When a user creates a stack, keep a cookie around for a while (2 weeks? 1 month?) that redirects requests for the homepage to the user's stack. This will aid in helping users to keep track of the stack they create if they forget to create a bookmark.

Alternate Idea: Instead of redirecting to the user's stack, show a modified version of the index page that includes a link to their existing stack.

Creation of days

In the old app, the GET handler for Days would create a new day if it didn't already exist. I think this is probably bad form. For the new app, the client should request a day, if it receives the proper error response, it will send a POST to create a new Day, then use that one. It's more RESTful...or something.

Mobile version does not properly collapse borders on index page

Stack creation