a3-wfryan

.gitignore

@@ -0,0 +1,3 @@
+package-lock.json
+/node_modules
+.env

README.md

@@ -1,114 +1,26 @@
-Assignment 3 - Persistence: Two-tier Web Application with Database, Express server, and CSS template
-===
+## Grocery Tracker
 
-Due: September 25nd, by 11:59 AM.
+http://grocerytracker.firescythe.net/
 
-This assignnment continues where we left off, extending it to use the most popular Node.js server framework (express), 
-a database (mongodb), and a CSS application framework / template of your choice (Boostrap, Material Design, Semantic UI, Pure etc.)
+Professor Roberts gave me an extension on this assignment.
+  So I was given an extension on this assignment but I ended up being sick a little longer than I anticapted and it took me longer to finish this because of that. So sorry for the extended delay!
 
-Baseline Requirements
----
+This is a basic grocery list maker. It keeps track of pricing per item and total price. You can reset the whole list and modify items in the list. It uses the CSS Flex/Flexbox for positioning certain elements on the page. To modify an item's price, enter a price in the price field, check the checkbox to the right of the item (or items, can modify multiple items at the same time), then click the Modify Item Price button. All items checked off will have their price in the list updated. I should note that its only the list itself that'll get the price updated. If you update the price of an item in the cart it won't reflect because it was added to the cart before the price change.
 
-Your application is required to implement the following functionalities:
+For the CSS framework I used Watercss. It's a very simple framework that took care of almost everything I needed for CSS. The only modifications I made were list styling (to remove bullets from an unordered list), positioning, and one specific text segment color.
 
-- a `Server`, created using Express (no alternatives will be accepted for this assignment)
-- a `Results` functionality which shows all data associated with a logged in user (except passwords)
-- a `Form/Entry` functionality which allows users to add, modify, and delete data items (must be all three!) associated with their user name / account. 
-- Persistent data storage in between server sessions using [mongodb](https://www.mongodb.com/cloud/atlas) (you *must* use mongodb for this assignment). You can use either the [official mongodb node.js library](https://www.npmjs.com/package/mongodb) or use the [Mongoose library](https://www.npmjs.com/package/mongoose), which enables you to define formal schemas for your database. Please be aware that the course staff cannot provide in-depth support for use of Mongoose.  
-- Use of a [CSS framework or template](https://github.com/troxler/awesome-css-frameworks). 
-This should do the bulk of your styling/CSS for you and be appropriate to your application. 
-For example, don't use [NES.css](https://nostalgic-css.github.io/NES.css/) (which is awesome!) unless you're creating a game or some type of retro 80s site.
+For middleware used, I used express.json, express-session, a custom function for redirecting back to login when not authenticated.
+Express.json parses the request body into json format making it easier simpler to handle server side.
+Express-session keeps track of login sessions and adds the appropriate information to requests and responses.
+I also use passportjs and passport-github to handle the oauth authentication. Passport serves as middleware to handle the oauth information for express and works with express-session to ensure the right information is maintained.
+The one I wrote simply redirects if the request session is invalid.
 
-Your application is required to demonstrate the use of the following concepts:  
-
-HTML:  
-- HTML input tags and form fields of various flavors (`<textarea>`, `<input>`, checkboxes, radio buttons etc.)
-- HTML that can display all data *for a particular authenticated user*. Note that this is different from the last assignnment, which required the display of all data in memory on the server.
-
-Note that it might make sense to have two pages for this assignment, one that handles login / authentication, and one that contains the rest of your application.
-For example, when visiting the home page for the assignment, users could be presented with a login form. After submitting the login form, if the login is 
-successful, they are taken to the main application. If they fail, they are sent back to the login to try again. For this assignment, it is acceptable to simply create 
-new user accounts upon login if none exist, however, you must alert your users to this fact.  
-
-CSS:  
-- CSS styling should primarily be provided by your chosen template/framework. 
-Oftentimes a great deal of care has been put into designing CSS templates; 
-don't override their stylesheets unless you are extremely confident in your graphic design capabilities. 
-The idea is to use CSS templates that give you a professional looking design aesthetic without requiring you to be a graphic designer yourself.
-
-JavaScript:  
-- At minimum, a small amount of front-end JavaScript to get / fetch data from the server. 
-See the [previous assignment](https://github.com/cs-4241-23/shortstack) for reference.
-
-Node.js:  
-- A server using Express and a persistent database (mongodb).
-
-General:  
-- Your site should achieve at least 90% on the `Performance`, `Best Practices`, `Accessibility`, and `SEO` tests 
-using Google [Lighthouse](https://developers.google.com/web/tools/lighthouse) (don't worry about the PWA test, and don't worry about scores for mobile devices).
-Test early and often so that fixing problems doesn't lead to suffering at the end of the assignment. 
-
-Deliverables
----
-
-Do the following to complete this assignment:
-
-1. Implement your project with the above requirements. I'd begin by converting your A2 assignment. First, change the server to use express. Then, modify the server to use mongodb instead of storing data locally. Last but not least, implement user accounts and login. User accounts and login is often the hardest part of this assignment, so budget your time accordingly.
-2. If you developed your project locally, deploy your project to Glitch (unless completing the alternative server technical acheivement described below), and fill in the appropriate fields in your package.json file.
-3. Test your project to make sure that when someone goes to your main page on Glitch (or an alternative server), it displays correctly.
-4. Ensure that your project has the proper naming scheme `a3-yourfirstname-yourlastname` so we can find it.
-5. Fork this repository and modify the README to the specifications below.
-6. Create and submit a Pull Request to the original repo. Name the pull request using the following template: `a3-firstname-lastname`.
-
-Acheivements
----
-
-Below are suggested technical and design achievements. You can use these to help boost your grade up to an A and customize the 
-assignment to your personal interests, for a maximum twenty additional points and a maximum grade of a 100%. 
-These are recommended acheivements, but feel free to create/implement your own... just make sure you thoroughly describe what you did in your README, 
-why it was challenging, and how many points you think the achievement should be worth. 
-ALL ACHIEVEMENTS MUST BE DESCRIBED IN YOUR README IN ORDER TO GET CREDIT FOR THEM.
-
-*Technical*
-- (10 points) Implement OAuth authentication, perhaps with a library like [passport.js](http://www.passportjs.org/). 
-*You must either use Github authenticaion or provide a username/password to access a dummy account*. 
-Course staff cannot be expected, for example, to have a personal Facebook, Google, or Twitter account to use when grading this assignment. 
-Please contact the course staff if you have any questions about this. THIS IS THE HARDEST ACHEIVEMENT OFFERED IN WEBWARE. You have been warned!  
-- (5 points) Instead of Glitch, host your site on a different service like [Heroku](https://www.heroku.com) or [Digital Ocean](https://www.digitalocean.com). Make sure to describe this a bit in your README. What was better about using the service you chose as compared to Glitch? What (if anything) was worse? 
-- (5 points) Get 100% (not 98%, not 99%, but 100%) in all four lighthouse tests required for this assignment.  
-
-*Design/UX*
-- (10 points) Make your site accessible using the [resources and hints available from the W3C](https://www.w3.org/WAI/), Implement/follow twelve tips from their [tips for writing](https://www.w3.org/WAI/tips/writing/), [tips for designing](https://www.w3.org/WAI/tips/designing/), and [tips for development](https://www.w3.org/WAI/tips/developing/). *Note that all twelve must require active work on your part*. 
-For example, even though your page will most likely not have a captcha, you don't get this as one of your twelve tips to follow because you're effectively 
-getting it "for free" without having to actively change anything about your site. 
-Contact the course staff if you have any questions about what qualifies and doesn't qualify in this regard. 
-List each tip that you followed and describe what you did to follow it in your site.
-- (5 points) Describe how your site uses the CRAP principles in the Non-Designer's Design Book readings. 
-Which element received the most emphasis (contrast) on each page? 
-How did you use proximity to organize the visual information on your page? 
-What design elements (colors, fonts, layouts, etc.) did you use repeatedly throughout your site? 
-How did you use alignment to organize information and/or increase contrast for particular elements. 
-Write a paragraph of at least 125 words *for each of four principles* (four paragraphs, 500 words in total). 
-
-Sample Readme (delete the above when you're ready to submit, and modify the below so with your links and descriptions)
----
-
-## Your Web Application Title
-
-your glitch (or alternative server) link e.g. http://a3-charlie-roberts.glitch.me
-
-Include a very brief summary of your project here. Images are encouraged, along with concise, high-level text. Be sure to include:
-
-- the goal of the application
-- challenges you faced in realizing the application
-- what authentication strategy you chose to use and why (choosing one because it seemed the easiest to implement is perfectly acceptable)
-- what CSS framework you used and why
-  - include any modifications to the CSS framework you made via custom CSS you authored
-- the five Express middleware packages you used and a short (one sentence) summary of what each one does. If you use a custom function for *one* (and one alone) middleware please 
-add a little more detail about what it does.
+I chose oauth with github for my authentication because of the challenge it imposed. This did cause me to take longer than I expected to but I couldn't be happier with what I learned from doing it. The biggest challenges I faced were oauth and lighthouse analysis adjustments.
 
 ## Technical Achievements
-- **Tech Achievement 1**: I used OAuth authentication via the GitHub strategy
+- **Tech Achievement 1**: Oauth via github! This was a pain but I got this running and I couldn't be prouder!
+- **Tech Achievement 2**: I also got it deployed using digital ocean lol
 
 ### Design/Evaluation Achievements
-- **Design Achievement 1**: I followed the following tips from the W3C Web Accessibility Initiative...
+- **Design Achievement 1**: 100 on all 4 Lighthouse categories! When I tested this locally I was able to obtain 100 on all 4 categories of the lighthouse analysis and I provided a screenshot in the assets directory.
+Deployed i get 100 in 3 and 92 in one category because I didn't get any ssl certificates so its using http not https

item_entry.json

@@ -0,0 +1,6 @@
+{
+    "_id": "ObjectId()",
+    "itemName": "itemName",
+    "price": 1.11,
+    "userID": "ObjectId()"
+}

old_server.js

@@ -0,0 +1,165 @@
+const http = require("http"),
+  fs = require("fs"),
+  // IMPORTANT: you must run `npm install` in the directory for this assignment
+  // to install the mime library if you're testing this on your local machine.
+  // However, Glitch will install it automatically by looking in your package.json
+  // file.
+  mime = require("mime"),
+  dir = "public/",
+  port = 3000;
+
+const appdata = [
+  { model: "toyota", year: 1999, mpg: 23 },
+  { model: "honda", year: 2004, mpg: 30 },
+  { model: "ford", year: 1987, mpg: 14 },
+];
+
+const totalPrice = { totalPrice: 0.0 };
+let retObject;
+
+const groceryList = [];
+
+const server = http.createServer(function (request, response) {
+
+  if (request.method === "GET") {
+    handleGet(request, response);
+  } else if (request.method === "POST") {
+    handlePost(request, response);
+  }else if (request.method === "DELETE") {
+    handleDelete(request, response);
+  }
+
+});
+
+const handleGet = function (request, response) {
+  const filename = dir + request.url.slice(1);
+
+  if (request.url === "/") {
+    sendFile(response, "public/index.html");
+  } else {
+    sendFile(response, filename);
+  }
+};
+
+const calcTotalPrice = function () {
+  totalPrice.totalPrice = 0.0;
+  if(groceryList.length !== 0){groceryList.forEach((item) => {
+    if (!isNaN(parseFloat(item.price))) {
+      totalPrice.totalPrice += parseFloat(item.price);
+    } else {
+      totalPrice.totalPrice += 0.0;
+    }
+  })};
+};
+
+const modifyPrice = function (data){
+  data.items.forEach(idx => {
+    console.log(groceryList[idx])
+    groceryList[idx].price = data.price;
+  })
+}
+const handlePost = function (request, response) {
+    let dataString = "";
+
+    request.on("data", function (data) {
+      dataString += data;
+    });
+
+    if(request.url ==="/submit")
+    {
+      request.on("end", function () {
+        const newItem = JSON.parse(dataString).item;
+        groceryList.push(newItem);
+        calcTotalPrice();
+        //console.log(totalPrice);
+        retObject = { groceryList, totalPrice };
+        console.log(retObject)
+        response.writeHead(200, "OK", { "Content-Type": "text/json" });
+        response.end(JSON.stringify(retObject));
+      });
+    }
+    else{
+      request.on("end", function () {
+        modifyPrice(JSON.parse(dataString))
+        calcTotalPrice();
+        retObject = { groceryList, totalPrice };
+        console.log(retObject)
+        response.writeHead(200, "OK", { "Content-Type": "text/json" });
+        response.end(JSON.stringify(retObject));
+      });
+    }
+
+
+};
+const deleteItems = function(data){
+  let temp = []
+  outerLoop: data.items.forEach(idx =>{
+    if(idx < groceryList.length){
+    innerLoop: for(let i = 0; i < groceryList.length; i++)
+    {
+      if(i !== idx){
+        temp.push(groceryList[i])
+      }
+      else{
+        groceryList.splice(idx, 1)
+      }
+    }}
+    else{
+      groceryList.splice(idx, 1)
+    }
+  });
+
+  console.log(temp)
+  groceryList.splice(0, groceryList.length);
+  temp.forEach(item =>{
+    groceryList.push(item)
+  });
+
+}
+const handleDelete = function (request, response) {
+
+  let dataString = "";
+
+  request.on("data", function (data) {
+    dataString += data;
+  });
+
+  if(request.url === "/reset"){
+  request.on("end", function () {
+    groceryList.splice(0, groceryList.length);
+    console.log(groceryList)
+    calcTotalPrice();
+    response.writeHead(200, "OK", { "Content-Type": "text/json" });
+    response.end(JSON.stringify(groceryList));
+  });}
+  else{
+    request.on("end", function () {
+      deleteItems(JSON.parse(dataString))
+      calcTotalPrice();
+      retObject = { groceryList, totalPrice };
+      console.log(retObject)
+      response.writeHead(200, "OK", { "Content-Type": "text/json" });
+      response.end(JSON.stringify(retObject));
+    });
+  }
+
+};
+
+const sendFile = function (response, filename) {
+  const type = mime.getType(filename);
+
+  fs.readFile(filename, function (err, content) {
+    // if the error = null, then we've loaded the file successfully
+    if (err === null) {
+      // status code: https://httpstatuses.com
+      response.writeHeader(200, { "Content-Type": type });
+      response.end(content);
+    } else {
+      // file not found, error code 404
+      response.writeHeader(404);
+      response.end("404 Error: File Not Found");
+    }
+  });
+};
+
+server.listen(process.env.PORT || port);

package.json

@@ -0,0 +1,20 @@
+{
+  "name": "",
+  "version": "",
+  "description": "",
+  "author": "",
+  "scripts": {
+    "start": "node server.js"
+  },
+  "dependencies": {
+    "cookie-session": "^2.0.0",
+    "dotenv": "^16.3.1",
+    "express": "^4.18.2",
+    "express-session": "^1.17.3",
+    "mime": "^2.6.0",
+    "mongodb": "^6.1.0",
+    "passport": "^0.6.0",
+    "passport-github": "^1.1.0",
+    "passport-github2": "^0.1.12"
+  }
+}

public/css/main.css

@@ -0,0 +1,54 @@
+body {
+  background: gray;
+  color:white;
+  font-family:"Oswald", sans-serif;
+  font-size: 14px;
+}
+h1{
+  font-family:"Oswald", serif;
+  font-size: 48px;
+  color:aquamarine;
+}
+.lists{
+  display: flex;
+  justify-content: flex-start;
+  padding-left:7rem
+}
+.groceryItem{
+  font-weight: 300;
+}
+label{
+  font-family: "Oswald", serif;
+}
+div#logout-box{
+  position:absolute;
+  right: 10rem;
+}
+#logout{
+  position:absolute;
+}
+#groceryList{
+  display: flex;
+  flex-direction:column;
+  list-style: none;
+  padding-left: 0;
+}
+
+#modbox-label{
+  padding-left: 1.5rem;
+}
+#cart-lab{
+  padding-left: 6rem;
+}
+#cartList{
+  display: flex;
+  flex-direction:column;
+  list-style: none;
+  padding-left: 0;
+}
+.errorMsg{
+  visibility: hidden;
+  display: none;
+  color:red;
+  font-size: 18px;
+}