alu/cse110-fa22-group29
1
0
Fork 0
mirror of https://github.com/cse110-fa22-group29/cse110-fa22-group29.git synced 2024-12-26 17:09:09 +00:00
Code Issues Packages Projects Releases Wiki Activity

updated css linter and html linter

Browse Source
This commit is contained in:
Marc 2022-11-13 06:11:56 +00:00
parent d6929af27e
commit 22d29718e8
28 changed files with 981 additions and 954 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

66
.eslintrc.json
View File

@ -1,33 +1,33 @@
{ {
"env": { "env": {
"browser": true, "browser": true,
"es2021": true, "es2021": true,
"node": true "node": true
}, },
"extends": "eslint:recommended", "extends": "eslint:recommended",
"overrides": [ "overrides": [
], ],
"parserOptions": { "parserOptions": {
"ecmaVersion": "latest", "ecmaVersion": "latest",
"sourceType": "module" "sourceType": "module"
}, },
"rules": { "rules": {
"indent": [ "indent": [
"error", "error",
"tab" "tab"
], ],
"linebreak-style": [ "linebreak-style": [
"error", "error",
"unix" "unix"
], ],
"quotes": [ "quotes": [
"error", "error",
"double" "double"
], ],
"semi": [ "semi": [
"error", "error",
"always" "always"
], ],
"no-global-assign": 0 "no-global-assign": 0
} }
} }

23
.github/workflows/css_linting.yml vendored Normal file
View File

@ -0,0 +1,23 @@
name: CSS Linting
on:
pull_request:
branches:
- main
# Allows you to run this workflow manually from the Actions tab
workflow_dispatch:
jobs:
# Single deploy job since we're just deploying
test:
runs-on: ubuntu-latest
steps:
- name: Install apt updates
run: sudo apt -y update; sudo apt -y upgrade;
- name: Checkout
uses: actions/checkout@v3
- name: Install dependencies
run: sudo npm install
- name: Run tests
run: sudo npm run lintCSS

86
.github/workflows/deploy-githubpages.yml vendored
View File

@ -1,43 +1,43 @@
# Simple workflow for deploying static content to GitHub Pages # Simple workflow for deploying static content to GitHub Pages
name: Deploy GitHub Pages name: Deploy GitHub Pages
on: on:
# Runs on pushes targeting the default branch # Runs on pushes targeting the default branch
push: push:
branches: branches:
- main - main
# Allows you to run this workflow manually from the Actions tab # Allows you to run this workflow manually from the Actions tab
workflow_dispatch: workflow_dispatch:
# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages # Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages
permissions: permissions:
contents: read contents: read
pages: write pages: write
id-token: write id-token: write
# Allow one concurrent deployment # Allow one concurrent deployment
concurrency: concurrency:
group: "pages" group: "pages"
cancel-in-progress: true cancel-in-progress: true
jobs: jobs:
# Single deploy job since we're just deploying # Single deploy job since we're just deploying
deploy: deploy:
environment: environment:
name: github-pages name: github-pages
url: ${{ steps.deployment.outputs.page_url }} url: ${{ steps.deployment.outputs.page_url }}
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- name: Checkout - name: Checkout
uses: actions/checkout@v3 uses: actions/checkout@v3
- name: Setup Pages - name: Setup Pages
uses: actions/configure-pages@v2 uses: actions/configure-pages@v2
- name: Upload artifact - name: Upload artifact
uses: actions/upload-pages-artifact@v1 uses: actions/upload-pages-artifact@v1
with: with:
# Upload only the src repository # Upload only the src repository
path: './source/' path: './source/'
- name: Deploy to GitHub Pages - name: Deploy to GitHub Pages
id: deployment id: deployment
uses: actions/deploy-pages@v1 uses: actions/deploy-pages@v1

48
.github/workflows/html-linting.yml vendored
View File

@ -1,25 +1,23 @@
name: HTML Linting name: HTML Linting
on: on:
pull_request: pull_request:
branches: branches:
- main - main
# Allows you to run this workflow manually from the Actions tab # Allows you to run this workflow manually from the Actions tab
workflow_dispatch: workflow_dispatch:
jobs: jobs:
# Single deploy job since we're just deploying # Single deploy job since we're just deploying
test: test:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- name: Install apt updates - name: Install apt updates
run: sudo apt -y update; sudo apt -y upgrade; run: sudo apt -y update; sudo apt -y upgrade;
- name: Install prerequisites - name: Checkout
run: sudo apt install -y htmlhint npm; uses: actions/checkout@v3
- name: Checkout - name: Install dependencies
uses: actions/checkout@v3 run: sudo npm install
- name: Install dependencies - name: Run tests
run: sudo npm install run: sudo npm run lintHTML
- name: Run tests
run: sudo npm run lintHTML

48
.github/workflows/js-linting.yml vendored
View File

@ -1,25 +1,25 @@
name: JS Linting name: JS Linting
on: on:
pull_request: pull_request:
branches: branches:
- main - main
# Allows you to run this workflow manually from the Actions tab # Allows you to run this workflow manually from the Actions tab
workflow_dispatch: workflow_dispatch:
jobs: jobs:
# Single deploy job since we're just deploying # Single deploy job since we're just deploying
test: test:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- name: Install apt updates - name: Install apt updates
run: sudo apt -y update; sudo apt -y upgrade; run: sudo apt -y update; sudo apt -y upgrade;
- name: Install prerequisites - name: Install prerequisites
run: sudo apt install -y nodejs npm; run: sudo apt install -y nodejs npm;
- name: Checkout - name: Checkout
uses: actions/checkout@v3 uses: actions/checkout@v3
- name: Install dependencies - name: Install dependencies
run: sudo npm install run: sudo npm install
- name: Run tests - name: Run tests
run: sudo npm run lint run: sudo npm run lint

48
.github/workflows/js-unittest.yml vendored
View File

@ -1,25 +1,25 @@
name: JS Unit Test name: JS Unit Test
on: on:
pull_request: pull_request:
branches: branches:
- main - main
# Allows you to run this workflow manually from the Actions tab # Allows you to run this workflow manually from the Actions tab
workflow_dispatch: workflow_dispatch:
jobs: jobs:
# Single deploy job since we're just deploying # Single deploy job since we're just deploying
test: test:
runs-on: ubuntu-latest runs-on: ubuntu-latest
steps: steps:
- name: Install apt updates - name: Install apt updates
run: sudo apt -y update; sudo apt -y upgrade; run: sudo apt -y update; sudo apt -y upgrade;
- name: Install prerequisites - name: Install prerequisites
run: sudo apt install -y nodejs npm; run: sudo apt install -y nodejs npm;
- name: Checkout - name: Checkout
uses: actions/checkout@v3 uses: actions/checkout@v3
- name: Install dependencies - name: Install dependencies
run: sudo npm install run: sudo npm install
- name: Run tests - name: Run tests
run: sudo npm test run: sudo npm test

4
.gitignore vendored
View File

@ -1,3 +1,3 @@
**/.devcontainer/* **/.devcontainer/*
**/node_modules/* **/node_modules/*
**/package-lock.json **/package-lock.json

6
.htmlhintrc
View File

@ -1,3 +1,3 @@
{ {
"attr-value-not-empty": false "attr-value-not-empty": false
} }

2
README.md
View File

@ -1,2 +1,2 @@
# cse110-fa22-group29 # cse110-fa22-group29
[Team Page Link](https://github.com/cse110-fa22-group29/cse110-fa22-group29/blob/main/admin/team.md) [Team Page Link](https://github.com/cse110-fa22-group29/cse110-fa22-group29/blob/main/admin/team.md)

94
admin/meetings/101122-kickoff.md
View File

@ -1,47 +1,47 @@
# Meeting Minutes (10/12/2022) # Meeting Minutes (10/12/2022)
## Team 29: Hackers1995 ## Team 29: Hackers1995
## Meeting Topic: Kickoff Meeting ## Meeting Topic: Kickoff Meeting
This meeting is being held to kickoff the start of many meetings to come during the quarter. This meeting is being held to kickoff the start of many meetings to come during the quarter.
## Attendance ## Attendance
1. Rhea Bhutada 1. Rhea Bhutada
2. George Dubinin 2. George Dubinin
3. Gavyn Ezell 3. Gavyn Ezell
4. Henry Feng 4. Henry Feng
5. Kara Hoagland 5. Kara Hoagland
6. Marc Reta 6. Marc Reta
7. Sanjit Joseph 7. Sanjit Joseph
8. Isaac Otero 8. Isaac Otero
9. Daniel Hernandez 9. Daniel Hernandez
## Absentees ## Absentees
1. Arthur Lu 1. Arthur Lu
## Meeting Details ## Meeting Details
- When: 10/12/2022 at 3:30PM - When: 10/12/2022 at 3:30PM
- Where: Zoom - Where: Zoom
## Agenda: ## Agenda:
- ### Old/Unresolved Business - ### Old/Unresolved Business
- N/A - N/A
- ### New Business - ### New Business
- go over github organization - go over github organization
- review assignments - review assignments
- go through rules - go through rules
- start branding/team name - start branding/team name
- ### Next Meeting's Business - ### Next Meeting's Business
- figure out roles - figure out roles
- decide weekly meeting times - decide weekly meeting times
- figure out team bonding events - figure out team bonding events
- brainstorm CRUD applications - brainstorm CRUD applications
- complete any remaining assignments - complete any remaining assignments
## Decisions Made ## Decisions Made
- went over github organizations and reviewed the assignments - went over github organizations and reviewed the assignments
- went through the rules and agreed on the contract - went through the rules and agreed on the contract
- figured out the brand name - figured out the brand name
## End Time ## End Time
- 10/12/2022 at 4:30PM - 10/12/2022 at 4:30PM

62
admin/meetings/101222-checkin1.md
View File

@ -1,32 +1,32 @@
# Meeting Minutes (10/12/2022) # Meeting Minutes (10/12/2022)
## Team 29: Hackers1995 ## Team 29: Hackers1995
## Meeting Topic: Weekly Check-In Meeting ## Meeting Topic: Weekly Check-In Meeting
This meeting is the first weekly meeting with TA This meeting is the first weekly meeting with TA
## Attendance ## Attendance
1. Gagan Gopalaiah 1. Gagan Gopalaiah
2. Rhea Bhutada 2. Rhea Bhutada
3. Kara Hoagland 3. Kara Hoagland
4. Marc Reta 4. Marc Reta
5. Arthur 5. Arthur
## Meeting Details ## Meeting Details
- When: 10/12/2022 at 8:00PM - When: 10/12/2022 at 8:00PM
- Where: Zoom - Where: Zoom
## Agenda: ## Agenda:
- ### Reviewed Project Details - ### Reviewed Project Details
- building CRUD app - building CRUD app
- utilizing HTML, CSS, JavaScript - utilizing HTML, CSS, JavaScript
- general domain is better than specific domain - general domain is better than specific domain
- ### Get Started early - ### Get Started early
- brainstorm CRUD apps - brainstorm CRUD apps
- review assignments - review assignments
- figure out unit test code - figure out unit test code
- familiarize yourself with GitHub Actions - familiarize yourself with GitHub Actions
## Important Information ## Important Information
- Gagan OH (6:30PM-7:30PM on Wednesday) in CSE Basement - Gagan OH (6:30PM-7:30PM on Wednesday) in CSE Basement
- Reserved the room if any of us want to meet there. TA not going to present unless required. - Reserved the room if any of us want to meet there. TA not going to present unless required.
## End Time ## End Time
- 10/12/2022 at 8:30PM - 10/12/2022 at 8:30PM

98
admin/meetings/101922-checkin2.md
View File

@ -1,50 +1,50 @@
# Meeting Minutes (10/19/2022) # Meeting Minutes (10/19/2022)
## Team 29: Hackers1995 ## Team 29: Hackers1995
## Meeting Topic: Weekly Check-In Meeting ## Meeting Topic: Weekly Check-In Meeting
This meeting is the second weekly meeting with TA. This meeting is the second weekly meeting with TA.
## Attendance ## Attendance
1. Gagan Gopalaiah 1. Gagan Gopalaiah
2. Rhea Bhutada 2. Rhea Bhutada
3. George Dubinin 3. George Dubinin
4. Kara Hoagland 4. Kara Hoagland
5. Marc Reta 5. Marc Reta
6. Arthur Lu 6. Arthur Lu
7. Gavyn Ezell 7. Gavyn Ezell
8. Isaac Otero 8. Isaac Otero
## Meeting Details ## Meeting Details
- When: 10/19/2022 at 8:00PM - When: 10/19/2022 at 8:00PM
- Where: Zoom - Where: Zoom
## Agenda: ## Agenda:
- ### Recap of last week - ### Recap of last week
- went over assignments - went over assignments
- discussed feelings on the midterm - discussed feelings on the midterm
- ### New Potential Meeting Time - ### New Potential Meeting Time
- without TA unless necessary - without TA unless necessary
- before lecture on Monday in CSE Basement - before lecture on Monday in CSE Basement
- ### Upcoming Assignments - ### Upcoming Assignments
- two coming up - two coming up
- brainstorm activity (due 10/23) - brainstorm activity (due 10/23)
- continue brainstorming throughout the week - continue brainstorming throughout the week
- due sunday - due sunday
- pitch (11/1) - pitch (11/1)
- initial draft by 10/25 - 10/26 - initial draft by 10/25 - 10/26
- ### Tips on Designing - ### Tips on Designing
- user center design - user center design
- define the problem first, then the tools/techniques - define the problem first, then the tools/techniques
- finalize on the product and its features, then decide on how to build it - finalize on the product and its features, then decide on how to build it
- ### Standup - ### Standup
- not expected everyday - not expected everyday
- once every two days is ideal - once every two days is ideal
- doesn't have to be too descriptive - doesn't have to be too descriptive
- ### Review of Recent Brainstorming Session - ### Review of Recent Brainstorming Session
## End Time ## End Time
- 10/19/2022 at 3:50PM - 10/19/2022 at 3:50PM

80
admin/meetings/102322-decision.md
View File

@ -1,40 +1,40 @@
# Meeting Minutes (10/23/2022) # Meeting Minutes (10/23/2022)
## Team 29: Hackers1995 ## Team 29: Hackers1995
## Meeting Topic: Application Final Decision ## Meeting Topic: Application Final Decision
This meeting is held to help the group decide on which kind of app to build. This meeting is held to help the group decide on which kind of app to build.
## Attendance ## Attendance
1. George Dubinin 1. George Dubinin
2. Henry Feng 2. Henry Feng
3. Arthur Lu 3. Arthur Lu
4. Marc Reta 4. Marc Reta
5. Kara Hoagland 5. Kara Hoagland
6. Rhea Bhutada 6. Rhea Bhutada
7. Isaac Otero 7. Isaac Otero
## Absentees ## Absentees
1. Sanjit Joseph 1. Sanjit Joseph
2. Gavyn Ezell 2. Gavyn Ezell
3. Daniel Hernandez 3. Daniel Hernandez
## Meeting Details ## Meeting Details
- When: - When:
- 10/23/2022 at 1:00PM - 10/23/2022 at 1:00PM
- Where: Zoom (Rhea's Meeting Room) - Where: Zoom (Rhea's Meeting Room)
## Agenda: ## Agenda:
- ### Old/Unresolved Business - ### Old/Unresolved Business
- N/A - N/A
- ### New Business - ### New Business
- Decide on a final app idea - Decide on a final app idea
- ### Next Meeting's Business - ### Next Meeting's Business
- Discuss design features for the chosen app - Discuss design features for the chosen app
## Decisions Made ## Decisions Made
- Maybe for the food reviewer app. Presenting possible writeup to Gagan - Maybe for the food reviewer app. Presenting possible writeup to Gagan
- Maybe for the resume builder. Presenting possible writeup to Gagan https://docs.google.com/document/d/1zdvVxd47Ivdz-D0rZGNJqc3D9GiQj0n_xMJKapOV39A/edit?usp=sharing - Maybe for the resume builder. Presenting possible writeup to Gagan https://docs.google.com/document/d/1zdvVxd47Ivdz-D0rZGNJqc3D9GiQj0n_xMJKapOV39A/edit?usp=sharing
- Maybe for Social Media Local Archive. Presenting possible writeup to Gagan https://docs.google.com/document/d/1upNr6lneB2uzCoQ12_aa1CMg1W8p2NBFb6xmP7i4-z4/edit?usp=sharing - Maybe for Social Media Local Archive. Presenting possible writeup to Gagan https://docs.google.com/document/d/1upNr6lneB2uzCoQ12_aa1CMg1W8p2NBFb6xmP7i4-z4/edit?usp=sharing
- No to the copy/paste app (not local first) - No to the copy/paste app (not local first)
## End Time ## End Time
- When: - When:
- 10/23/2022 at 2:00PM - 10/23/2022 at 2:00PM

88
admin/meetings/102622-checkin3.md
View File

@ -1,44 +1,44 @@
# Meeting Minutes (10/26/2022) # Meeting Minutes (10/26/2022)
## Team 29: Hackers1995 ## Team 29: Hackers1995
## Meeting Topic: Weekly Check-In Meeting ## Meeting Topic: Weekly Check-In Meeting
This is our third weekly meeting with Gagan. This is our third weekly meeting with Gagan.
## Attendance ## Attendance
TA. Gagan Gopalaiah TA. Gagan Gopalaiah
1. Rhea Bhutada 1. Rhea Bhutada
2. George Dubinin 2. George Dubinin
3. Sanjit Joseph 3. Sanjit Joseph
4. Arthur Lu 4. Arthur Lu
5. Gavyn Ezell 5. Gavyn Ezell
## Meeting Details ## Meeting Details
- When: 10/26/2022 at 3:00 PM - When: 10/26/2022 at 3:00 PM
- Where: Zoom (Gagan's Zoom room: https://ucsd.zoom.us/j/5177090642) - Where: Zoom (Gagan's Zoom room: https://ucsd.zoom.us/j/5177090642)
## Agenda: ## Agenda:
- ### Present our ideas to Gagan - ### Present our ideas to Gagan
- All ideas seem to be doable - All ideas seem to be doable
- Consider a few tweaks to "CRUDify" apps - Consider a few tweaks to "CRUDify" apps
- Gagan is partial to food review app idea, but any of them can work - Gagan is partial to food review app idea, but any of them can work
- ### Tips for projects - ### Tips for projects
- SOCIAL MEDIA ORGANIZER: avoid API integration if possible/only make it a small part, not a main feature - SOCIAL MEDIA ORGANIZER: avoid API integration if possible/only make it a small part, not a main feature
- RESUME BUILDER: try to "CRUDify" it more if we're going for this - RESUME BUILDER: try to "CRUDify" it more if we're going for this
- ### Standups - ### Standups
- Once per 2 days, 3 in worst case - Once per 2 days, 3 in worst case
- Perhaps make a separate slack channel for these to avoid clutter - Perhaps make a separate slack channel for these to avoid clutter
## Moving forward: ## Moving forward:
- ### BY FRIDAY: - ### BY FRIDAY:
- Try and meet tomorrow (10/27) to make a final decision - Try and meet tomorrow (10/27) to make a final decision
- Let Gagan know what we've decided on - Let Gagan know what we've decided on
- Complete project pitch assignment - need to present to Gagan tomorrow 10/27, due on canvas 11/1 - Complete project pitch assignment - need to present to Gagan tomorrow 10/27, due on canvas 11/1
- ### OVER WEEKEND: - ### OVER WEEKEND:
- (If possible) Start on CI/CD pipeline (basic js app/unit tests, use Github actions to set up) - (If possible) Start on CI/CD pipeline (basic js app/unit tests, use Github actions to set up)
## End Time ## End Time
- 10/26/2022 at 4:00 PM - 10/26/2022 at 4:00 PM

120
admin/meetings/102722-final_decision.md
View File

@ -1,60 +1,60 @@
# Meeting Minutes (10/27/2022) # Meeting Minutes (10/27/2022)
## Team 29: Hackers1995 ## Team 29: Hackers1995
## Meeting Topic: Final Project Decision ## Meeting Topic: Final Project Decision
We're figuring out what project we're going to do, and figure out what we need for the starting pitch. We're figuring out what project we're going to do, and figure out what we need for the starting pitch.
## Attendance ## Attendance
1. Rhea Bhutada 1. Rhea Bhutada
2. Sanjit Joseph 2. Sanjit Joseph
3. Arthur Lu 3. Arthur Lu
4. Henry Feng 4. Henry Feng
5. Marc Reta 5. Marc Reta
6. Kara Hoagland 6. Kara Hoagland
7. Daniel Hernandez 7. Daniel Hernandez
8. Gavyn Ezell 8. Gavyn Ezell
9. Isaac Otero 9. Isaac Otero
## Meeting Details ## Meeting Details
- When: 10/27/2022 at 5:00 PM - When: 10/27/2022 at 5:00 PM
- Where: Zoom (Rhea's Zoom room: https://ucsd.zoom.us/j/8054288343) - Where: Zoom (Rhea's Zoom room: https://ucsd.zoom.us/j/8054288343)
## Agenda: ## Agenda:
- ### Decide which project we're doing - ### Decide which project we're doing
- Gagan seemed to like the food review app idea best in their current states - Gagan seemed to like the food review app idea best in their current states
- We all seem to agree that the food review app is acceptable - We all seem to agree that the food review app is acceptable
- Made a couple clarifications, no major changes or objections to the app - Made a couple clarifications, no major changes or objections to the app
- ### Start project pitch - ### Start project pitch
- Created google slides: **https://docs.google.com/presentation/d/1_XWihJGVChFtYS38RnYJtQUuFKsgvewOCOkdeMHFRg4/edit?usp=sharing** - Created google slides: **https://docs.google.com/presentation/d/1_XWihJGVChFtYS38RnYJtQUuFKsgvewOCOkdeMHFRg4/edit?usp=sharing**
- Prof recommends skimming the book: **https://basecamp.com/shapeup** (esp. ch.5 on risks and rabbit holes) - Prof recommends skimming the book: **https://basecamp.com/shapeup** (esp. ch.5 on risks and rabbit holes)
- Finishing Risks + Rabbit holes here in the meeting - Finishing Risks + Rabbit holes here in the meeting
- Kara posted a design prototype in Slack: https://cse110fall2022.slack.com/archives/C04598WA7P1/p1666918573779859 - Kara posted a design prototype in Slack: https://cse110fall2022.slack.com/archives/C04598WA7P1/p1666918573779859
- ### App Description - ### App Description
- Renaming it to a "Food Diary" app, not limited to UCSD - Renaming it to a "Food Diary" app, not limited to UCSD
- Allows users to store info about recent foods, restaurant name, location, price, your rating etc. - Allows users to store info about recent foods, restaurant name, location, price, your rating etc.
- Probably provides food suggestions based on where you've eaten (and liked) before - Probably provides food suggestions based on where you've eaten (and liked) before
- We're not going to try anything with external data atm. - We're not going to try anything with external data atm.
## Moving forward: ## Moving forward:
- ### BY TOMORROW: - ### BY TOMORROW:
- FINISH PITCH SLIDES - FINISH PITCH SLIDES
- MUST CHANGE DIAGRAM TO ALL RESTAURANTS (Isaac will change this) - MUST CHANGE DIAGRAM TO ALL RESTAURANTS (Isaac will change this)
- Daniel will update the pitch slides by adding images/graphics. - Daniel will update the pitch slides by adding images/graphics.
- Daniel + Sanjit are doing visual representation. - Daniel + Sanjit are doing visual representation.
- Gayvn is doing potential competitors - Gayvn is doing potential competitors
- Henry, Sanjit, Kara are doing user personas - Henry, Sanjit, Kara are doing user personas
- Rhea is doing statement + purpose - Rhea is doing statement + purpose
- Arthur + Marc are doing "why it's a CRUD app" - Arthur + Marc are doing "why it's a CRUD app"
- See if we can have a short meeting tomorrow before meeting Gagan just to review our pitch. - See if we can have a short meeting tomorrow before meeting Gagan just to review our pitch.
- Put all components in specs folder before pitch - Put all components in specs folder before pitch
- Meet at 2:30? Meeting with Gagan is probably at 3:30 - Meet at 2:30? Meeting with Gagan is probably at 3:30
- ### LATER: - ### LATER:
- Have some people split off and work on the basic UI design. Technically Sanjit had the 'art role' according to the TA but not sure what that entails. More ppl would def be helpful. TBD who else is helping - Have some people split off and work on the basic UI design. Technically Sanjit had the 'art role' according to the TA but not sure what that entails. More ppl would def be helpful. TBD who else is helping
## End Time ## End Time
- 10/27/2022 at 6:15 PM - 10/27/2022 at 6:15 PM

48
admin/meetings/102822-project_pitch.md
View File

@ -1,24 +1,24 @@
# Meeting Minutes (10/28/2022) # Meeting Minutes (10/28/2022)
## Team 29: Hackers1995 ## Team 29: Hackers1995
## Meeting Topic: Project Pitch ## Meeting Topic: Project Pitch
We finished up the project pitch docs and presenting them to Gagan. We finished up the project pitch docs and presenting them to Gagan.
Google slides: **https://docs.google.com/presentation/d/1_XWihJGVChFtYS38RnYJtQUuFKsgvewOCOkdeMHFRg4/edit?usp=sharing** Google slides: **https://docs.google.com/presentation/d/1_XWihJGVChFtYS38RnYJtQUuFKsgvewOCOkdeMHFRg4/edit?usp=sharing**
## Meeting Details ## Meeting Details
- When: 10/28/2022 at 2:30 PM - When: 10/28/2022 at 2:30 PM
- Where: Zoom (Rhea's Zoom room: https://ucsd.zoom.us/j/8054288343) - Where: Zoom (Rhea's Zoom room: https://ucsd.zoom.us/j/8054288343)
## Agenda: ## Agenda:
- ### Finish Project Pitch documents - ### Finish Project Pitch documents
- Finished user stories/diagrams and uploaded to github - Finished user stories/diagrams and uploaded to github
- Went over presentation before showing TA - Went over presentation before showing TA
- Presented project to Gagan - Presented project to Gagan
- **Overall reaction - he liked our app! More feedback to come, but we can feel free to start some basic work.** - **Overall reaction - he liked our app! More feedback to come, but we can feel free to start some basic work.**
## Moving forward: ## Moving forward:
- I think we need to upload our project pitch to canvas by 11/1 - I think we need to upload our project pitch to canvas by 11/1
- Start on the really basic stuff as discussed in lecture (hello world for CI/CD setup, etc) - Start on the really basic stuff as discussed in lecture (hello world for CI/CD setup, etc)
## End Time ## End Time
- 10/28/2022 at 4:00 PM - 10/28/2022 at 4:00 PM

82
admin/meetings/110122-meeting.md
View File

@ -1,41 +1,41 @@
# Meeting Minutes (11/01/2022) # Meeting Minutes (11/01/2022)
## Team 29: Hackers1995 ## Team 29: Hackers1995
## Meeting Topic: Work going forward ## Meeting Topic: Work going forward
We're trying to figure out what our goals are for the project and how to get started. We're trying to figure out what our goals are for the project and how to get started.
## Meeting Details ## Meeting Details
- When: 11/01/2022 at 7:00 PM - When: 11/01/2022 at 7:00 PM
- Where: Zoom (Rhea's Zoom room: https://ucsd.zoom.us/j/8054288343) - Where: Zoom (Rhea's Zoom room: https://ucsd.zoom.us/j/8054288343)
## Attendance ## Attendance
1. Rhea 1. Rhea
2. Gavyn 2. Gavyn
3. Isaac 3. Isaac
4. Kara 4. Kara
5. Marc 5. Marc
6. Henry 6. Henry
7. Daniel 7. Daniel
8. Sanjit 8. Sanjit
## Notes: ## Notes:
- Gagan suggests we have a feature backlog and pull stuff from that - Gagan suggests we have a feature backlog and pull stuff from that
- Using Github Issues for our feature backlog - Using Github Issues for our feature backlog
- Perhaps integrate TTS from Lab5 into something (pick a random restaurant while driving, etc) - Perhaps integrate TTS from Lab5 into something (pick a random restaurant while driving, etc)
- Created figma sketch for app design, uploaded to github and google slides - Created figma sketch for app design, uploaded to github and google slides
## Moving forward: ## Moving forward:
- ### BY TONIGHT: - ### BY TONIGHT:
- We'll submit our pitch files - We'll submit our pitch files
- ### LATER: - ### LATER:
- Sanjit will upload a basic hello world program in order to test deployment/github actions - Sanjit will upload a basic hello world program in order to test deployment/github actions
- Arthur will start figuring out how to configure github actions - Arthur will start figuring out how to configure github actions
- ### PREFERENCES: - ### PREFERENCES:
- BACKEND: Henry, Gavyn, Kara - BACKEND: Henry, Gavyn, Kara
- FRONTEND: Isaac - FRONTEND: Isaac
- NO PREFERENCE: Daniel, Marc, Rhea, Sanjit - NO PREFERENCE: Daniel, Marc, Rhea, Sanjit
## End Time ## End Time
- 11/01/2022 at 9:00 PM - 11/01/2022 at 9:00 PM

68
admin/meetings/110222-checkin4.md
View File

@ -1,34 +1,34 @@
# Meeting Minutes (11/02/2022) # Meeting Minutes (11/02/2022)
## Team 29: Hackers1995 ## Team 29: Hackers1995
## Meeting Topic: Weekly TA Catchup with Gagan ## Meeting Topic: Weekly TA Catchup with Gagan
We are meeting with Gagan to discuss early phase design concepts and decisions we need to think about as we start the early coding phase. We are meeting with Gagan to discuss early phase design concepts and decisions we need to think about as we start the early coding phase.
## Attendance ## Attendance
1. Rhea Bhutada 1. Rhea Bhutada
2. George Dubinin 2. George Dubinin
3. Gagan Gopalaiah 3. Gagan Gopalaiah
## Meeting Details ## Meeting Details
- When: 11/02/2022 at 3:30PM - When: 11/02/2022 at 3:30PM
- Where: Zoom - Where: Zoom
## Agenda: ## Agenda:
## Discussion Points by Gagan ## Discussion Points by Gagan
- Now that we finished designs stage there are 2 approaches - Now that we finished designs stage there are 2 approaches
- The first is to just start coding without thinking about design (cowboy coding). It works but can get bumpy down the road - The first is to just start coding without thinking about design (cowboy coding). It works but can get bumpy down the road
- The second is to look at the project from a birds eye view and break it down into milestones and tasks. First break it down into weeks and then decide on what to do each day of the week. This will make it easier to keep things organized. - The second is to look at the project from a birds eye view and break it down into milestones and tasks. First break it down into weeks and then decide on what to do each day of the week. This will make it easier to keep things organized.
- Jira and GitHub issues will be super helpful. Jira is a more expensive option so instead prof recommends creating issues. - Jira and GitHub issues will be super helpful. Jira is a more expensive option so instead prof recommends creating issues.
- Start thinking about storage options. Think local first and decide on options like: - Start thinking about storage options. Think local first and decide on options like:
- locally stored json files - locally stored json files
- browser local storage - browser local storage
- "real" database like IndexDB - "real" database like IndexDB
- Think about different models to keep track of changes and versions. Consider the branching model (one central repository and everyone has a branch or one breanch per feature) and the forking model (the central repository is copied and developers work in these copies and push changes to their own copies before syncing to the central repo). Useful info here: https://www.flagship.io/git-branching-strategies/ - Think about different models to keep track of changes and versions. Consider the branching model (one central repository and everyone has a branch or one breanch per feature) and the forking model (the central repository is copied and developers work in these copies and push changes to their own copies before syncing to the central repo). Useful info here: https://www.flagship.io/git-branching-strategies/
- Think about how pull requests will be approved and create a system for PR review and suggests. - Think about how pull requests will be approved and create a system for PR review and suggests.
- Break down the project and decide on which tasks to be completed. Then decide on how long sprints will last and how tasks will be assigned. - Break down the project and decide on which tasks to be completed. Then decide on how long sprints will last and how tasks will be assigned.
- We need to create the ADR and place it in the brainstorming section of the repo. This will contain details about specific project decisions that we made like database decisions (for example). - We need to create the ADR and place it in the brainstorming section of the repo. This will contain details about specific project decisions that we made like database decisions (for example).
## End Time ## End Time
- 11/02/2022 at 4:00PM - 11/02/2022 at 4:00PM

72
admin/meetings/110922-checkin5.md
View File

@ -1,36 +1,36 @@
# Meeting Minutes (11/09/2022) # Meeting Minutes (11/09/2022)
## Team 29: Hackers1995 ## Team 29: Hackers1995
## Meeting Topic: Weekly TA Catchup with Gagan ## Meeting Topic: Weekly TA Catchup with Gagan
We are meeting with Gagan to discuss progress made on Sprint 1 and testing strategies that we need to keep in mind as we continue developing. We are meeting with Gagan to discuss progress made on Sprint 1 and testing strategies that we need to keep in mind as we continue developing.
## Attendance ## Attendance
1. Rhea Bhutada 1. Rhea Bhutada
2. George Dubinin 2. George Dubinin
3. Gagan Gopalaiah 3. Gagan Gopalaiah
4. Sanjit Joseph 4. Sanjit Joseph
## Meeting Details ## Meeting Details
- When: 11/09/2022 at 3:30PM - When: 11/09/2022 at 3:30PM
- Where: Zoom - Where: Zoom
## Agenda: ## Agenda:
## Discussion Points by Gagan ## Discussion Points by Gagan
- Provided updates on first sprint - Provided updates on first sprint
- Testing Tips - Testing Tips
- functionality testing - functionality testing
- test one feature - test one feature
- test individual functions - test individual functions
- static testing - static testing
- checking if its meeting the conventions and standards for specific programming language - checking if its meeting the conventions and standards for specific programming language
- linting - linting
- specific to programming language - specific to programming language
- overall - overall
- if tested properly, we reduce problems end-to-end testing - if tested properly, we reduce problems end-to-end testing
- Documentation - Documentation
- What the code does? - What the code does?
- What the file is for? - What the file is for?
- JS Docs - JS Docs
## End Time ## End Time
- 11/09/2022 at 4:00PM - 11/09/2022 at 4:00PM

82
admin/meetings/11722-sprint1.md
View File

@ -1,41 +1,41 @@
# Meeting Minutes (11/07/2022) # Meeting Minutes (11/07/2022)
## Team 29: Hackers1995 ## Team 29: Hackers1995
## Meeting Topic: First Sprint ## Meeting Topic: First Sprint
Meeting notes for the first sprint Meeting notes for the first sprint
## Attendance ## Attendance
1. Rhea Bhutada 1. Rhea Bhutada
2. George Dubinin 2. George Dubinin
3. Gavyn Ezell 3. Gavyn Ezell
4. Henry Feng 4. Henry Feng
5. Kara Hoagland 5. Kara Hoagland
6. Marc Reta 6. Marc Reta
7. Sanjit Joseph 7. Sanjit Joseph
8. Daniel Hernandez 8. Daniel Hernandez
9. Arthur Lu 9. Arthur Lu
## Absentees ## Absentees
1. Isaac Otero 1. Isaac Otero
## Meeting Details ## Meeting Details
- When: 11/07/2022 at 6:00PM - When: 11/07/2022 at 6:00PM
- Where: CSE Building Second Floor - Where: CSE Building Second Floor
## Agenda: ## Agenda:
- ### Old/Unresolved Business - ### Old/Unresolved Business
- N/A - N/A
- ### New Business - ### New Business
- The first sprint: - The first sprint:
- Create more Gitflows and automation. Verify current workflows and actions - Create more Gitflows and automation. Verify current workflows and actions
- Determine interface details for the app (user experience) - Determine interface details for the app (user experience)
- Start on the backend - Start on the backend
- ### Next Meeting's Business - ### Next Meeting's Business
## Decisions Made ## Decisions Made
- Linting details decided (TABS NOT SPACES) - Linting details decided (TABS NOT SPACES)
## End Time ## End Time
- 11/07/2022 at 8:00PM - 11/07/2022 at 8:00PM

114
admin/misc/rules.md
View File

@ -1,57 +1,57 @@
# Team Working Agreement # Team Working Agreement
## Term: Fall 2022 ## Term: Fall 2022
## Creation: 10/12/2022; Revised: N/A ## Creation: 10/12/2022; Revised: N/A
## Group Identification ## Group Identification
- Team 29 - Team 29
- TA: Gagan Gopalaiah - TA: Gagan Gopalaiah
- Instructor: Professor Thomas Powell - Instructor: Professor Thomas Powell
- Team Name: Hackers1995 - Team Name: Hackers1995
## Team member info (name/email) ## Team member info (name/email)
1. Rhea Bhutada, rbhutada@ucsd.edu 1. Rhea Bhutada, rbhutada@ucsd.edu
2. George Dubinin, gdubinin@ucsd.edu 2. George Dubinin, gdubinin@ucsd.edu
3. Gavyn Ezell, gezell@ucsd.edu 3. Gavyn Ezell, gezell@ucsd.edu
4. Henry Feng, hefeng@ucsd.edu 4. Henry Feng, hefeng@ucsd.edu
5. Kara Hoagland, khoaglan@ucsd.edu 5. Kara Hoagland, khoaglan@ucsd.edu
6. Marc Reta, mreta@ucsd.edu 6. Marc Reta, mreta@ucsd.edu
7. Sanjit Joseph, smjoseph@ucsd.edu 7. Sanjit Joseph, smjoseph@ucsd.edu
8. Isaac Otero, irotero@ucsd.edu 8. Isaac Otero, irotero@ucsd.edu
9. Arthur Lu, a8lu@ucsd.edu 9. Arthur Lu, a8lu@ucsd.edu
10. Daniel Hernandez, d7hernan@ucsd.edu 10. Daniel Hernandez, d7hernan@ucsd.edu
## RULES: ## RULES:
#### 1) Primary Means of Communication and Expectations #### 1) Primary Means of Communication and Expectations
- All members will communicate via Slack. - All members will communicate via Slack.
- All members will be expected to read messages from group chats and direct messages, and respond in no more than 4 hours and no later than 10PM. - All members will be expected to read messages from group chats and direct messages, and respond in no more than 4 hours and no later than 10PM.
- All pull requests require 3 people to review the code being pushed to main. - All pull requests require 3 people to review the code being pushed to main.
#### 2) Scheduling Meetings (Schedule at least one meeting as part of constructing your team agreement.) #### 2) Scheduling Meetings (Schedule at least one meeting as part of constructing your team agreement.)
- Members are expected to meet at least once a week with the group either in-person or on Zoom. Future meeting details will be determined within a 24 hours window. - Members are expected to meet at least once a week with the group either in-person or on Zoom. Future meeting details will be determined within a 24 hours window.
- Team members hosting the meeting will send out a reminder of the meeting with an agenda 2 hours before the meeting. - Team members hosting the meeting will send out a reminder of the meeting with an agenda 2 hours before the meeting.
#### 3) General Responsibilities for All Team Members #### 3) General Responsibilities for All Team Members
- Respect the contributions of others. - Respect the contributions of others.
- Work on assignments early to allow others to review and debug any issues. - Work on assignments early to allow others to review and debug any issues.
- Communicate any issues or problems as early as possible. - Communicate any issues or problems as early as possible.
- Be open to criticism. - Be open to criticism.
#### 4) Specific Team Member Responsibilities/Deadlines (Optional) #### 4) Specific Team Member Responsibilities/Deadlines (Optional)
- A daily standup is required every day from every team member. A daily standup includes what you've completed, what you want to work on, and what issues you encountered for the day. If you haven't done anything for that day, write down what you will be contributing. - A daily standup is required every day from every team member. A daily standup includes what you've completed, what you want to work on, and what issues you encountered for the day. If you haven't done anything for that day, write down what you will be contributing.
#### 5) Conflict Resolution #### 5) Conflict Resolution
- Conflicts between individuals will first try to be resolved amongst the people involved. - Conflicts between individuals will first try to be resolved amongst the people involved.
- Group conflicts will be voted on. - Group conflicts will be voted on.
- Ongoing conflicts will be reported to the TA. - Ongoing conflicts will be reported to the TA.
- Unprofessionalism of any kind will not be tolerated. Conflicts involving this will immediately be brought up with the TA - Unprofessionalism of any kind will not be tolerated. Conflicts involving this will immediately be brought up with the TA
#### 6) Expectations of Faculty and GTA’s #### 6) Expectations of Faculty and GTA’s
- If a team member fails to live up to this agreement, the situation may be reported to the staff, but the team will still be responsible for submitting a completed assignment. Staff will be available to meet with teams to resolve issues. - If a team member fails to live up to this agreement, the situation may be reported to the staff, but the team will still be responsible for submitting a completed assignment. Staff will be available to meet with teams to resolve issues.
## Team Signatures ## Team Signatures
#### Print Name: #### Print Name:
#### Signature: #### Signature:

146
admin/team.md
View File

@ -1,73 +1,73 @@
# **Hackers1995** # **Hackers1995**
## **Brand** ## **Brand**
![poster](./branding/teamposter.jpg) ![poster](./branding/teamposter.jpg)
## **Values** ## **Values**
- Openness - Openness
- Honesty - Honesty
- Respect - Respect
- Integrity - Integrity
- Diversity/Inclusion - Diversity/Inclusion
## **Roster** ## **Roster**
### **TA: Gagan Gopalaiah** ### **TA: Gagan Gopalaiah**
### **Team Lead: Rhea Bhutada** ### **Team Lead: Rhea Bhutada**
- #### About Me: - #### About Me:
- My name is Rhea Bhutada and I am currently a CS major and CogSci minor at ERC. The intersection between neuroscience and computer science really fascinates me and I generally try to apply myself to projects that deal with the overlap of both of these fields. This year I'm working as an undergraduate researcher at the Swartz Center for Computational Neuroscience, which has been an extremely cool experience. Other than that I love to stay active. I used to play basketball in high school and was in an NCAA commercial with Shaq. But lately, I’ve been really into running. Overall, I'm excited to contribute to this project! Although I haven't had too much industry experience, I am interested to see how I can apply my previous course work to backend or frontend design. - My name is Rhea Bhutada and I am currently a CS major and CogSci minor at ERC. The intersection between neuroscience and computer science really fascinates me and I generally try to apply myself to projects that deal with the overlap of both of these fields. This year I'm working as an undergraduate researcher at the Swartz Center for Computational Neuroscience, which has been an extremely cool experience. Other than that I love to stay active. I used to play basketball in high school and was in an NCAA commercial with Shaq. But lately, I’ve been really into running. Overall, I'm excited to contribute to this project! Although I haven't had too much industry experience, I am interested to see how I can apply my previous course work to backend or frontend design.
- #### Link to Github: https://github.com/rheabhutada02 - #### Link to Github: https://github.com/rheabhutada02
### **Team Lead: George Dubinin** ### **Team Lead: George Dubinin**
- #### About Me: - #### About Me:
- Hello World! I'm a fifth year (3rd year transfer) computer science major from the North Bay Area. Web development has been a big focus of mine since taking Prof Powell's 134B last winter and I'm stoked to be back in the "full stack" developer seat for 110. I am the second the team lead and in addition to my love for leading and working on team projects I am also fascinated by web development technologies including containerization, infrastructure as code (IaC), software as a service (SAAS), and web-based encryption (security). I am also an avid DJ and the traininer manmager for the DJ club on campus. This quarter is shaping up to be a memorable one! - Hello World! I'm a fifth year (3rd year transfer) computer science major from the North Bay Area. Web development has been a big focus of mine since taking Prof Powell's 134B last winter and I'm stoked to be back in the "full stack" developer seat for 110. I am the second the team lead and in addition to my love for leading and working on team projects I am also fascinated by web development technologies including containerization, infrastructure as code (IaC), software as a service (SAAS), and web-based encryption (security). I am also an avid DJ and the traininer manmager for the DJ club on campus. This quarter is shaping up to be a memorable one!
- #### Link to Github: https://github.com/look-its-ashton - #### Link to Github: https://github.com/look-its-ashton
### **Gavyn Ezell** ### **Gavyn Ezell**
- #### About Me: - #### About Me:
- My name is Gavyn Ezell and I’m from Hawaii. Currently a 3rd year CS Major at Muir. I love video games, playing piano, and going to the gym. For SWE, backend interests me most (I am not good with design and visuals), and I’m hoping to learn a lot more backend from this project! - My name is Gavyn Ezell and I’m from Hawaii. Currently a 3rd year CS Major at Muir. I love video games, playing piano, and going to the gym. For SWE, backend interests me most (I am not good with design and visuals), and I’m hoping to learn a lot more backend from this project!
- #### Link to Github: https://github.com/gavyn-ezell - #### Link to Github: https://github.com/gavyn-ezell
### **Daniel Hernandez** ### **Daniel Hernandez**
- #### About Me: - #### About Me:
- My name is Daniel Hernandez and I am a 3rd year Computer Science major and music minor. Some of my interests in the CS field are ML, AI, and Cybersecurity. Outside of school, I play drums for a local band. For SE, the backend aspect appeals to me the most since I am able to utilize more of what I learned from my past classes. However, I would want to try frontend since I do enjoy design to some extent. - My name is Daniel Hernandez and I am a 3rd year Computer Science major and music minor. Some of my interests in the CS field are ML, AI, and Cybersecurity. Outside of school, I play drums for a local band. For SE, the backend aspect appeals to me the most since I am able to utilize more of what I learned from my past classes. However, I would want to try frontend since I do enjoy design to some extent.
- #### Link to Github: https://github.com/d7hernan - #### Link to Github: https://github.com/d7hernan
### **Henry Feng** ### **Henry Feng**
- #### About Me: - #### About Me:
- My name is Henry, and I am a 3rd year CS major. I was born in China and grew up in New Zealand. I wrote my first line of code, in Python during my second year of high school. My favourite foods are ramen, steak and pasta. Some of my hobbies include playing guitar, hiking, cooking, video games, and music (from the Persona series). I am excited to start this project and hope to contribute to both frontend and backend. - My name is Henry, and I am a 3rd year CS major. I was born in China and grew up in New Zealand. I wrote my first line of code, in Python during my second year of high school. My favourite foods are ramen, steak and pasta. Some of my hobbies include playing guitar, hiking, cooking, video games, and music (from the Persona series). I am excited to start this project and hope to contribute to both frontend and backend.
- #### Link to Github: https://github.com/dusk-moon - #### Link to Github: https://github.com/dusk-moon
### **Kara Hoagland** ### **Kara Hoagland**
- #### About Me: - #### About Me:
- My name is Kara Hoagland and I am a 3rd year Computer Engineering major. CS-wise, I'm interested in topics such as computer vision and RFID, but it's hard to limit oneself because there's so many interesting topics out there. Outside of CS, I enjoy D&D, biking, and reading. I got some industry experience over summer and love getting to see how that experience and my previous classes all apply to this project. I'm interested in full stack but more so the backend of things. - My name is Kara Hoagland and I am a 3rd year Computer Engineering major. CS-wise, I'm interested in topics such as computer vision and RFID, but it's hard to limit oneself because there's so many interesting topics out there. Outside of CS, I enjoy D&D, biking, and reading. I got some industry experience over summer and love getting to see how that experience and my previous classes all apply to this project. I'm interested in full stack but more so the backend of things.
- #### Link to Github: https://github.com/KH-Cl - #### Link to Github: https://github.com/KH-Cl
### **Marc Reta** ### **Marc Reta**
- #### About Me: My name is Marc Reta and I am a 3rd year Computer Engineering major in Warren College. I love exploring San Diego and going on adventures. I have a huge interest in Public Transportation. I'm looking foward to working with everyone in my group and learn how to create an application. - #### About Me: My name is Marc Reta and I am a 3rd year Computer Engineering major in Warren College. I love exploring San Diego and going on adventures. I have a huge interest in Public Transportation. I'm looking foward to working with everyone in my group and learn how to create an application.
- #### Link to Github: https://github.com/Graydogminer - #### Link to Github: https://github.com/Graydogminer
### **Sanjit Joseph** ### **Sanjit Joseph**
- #### About Me: - #### About Me:
- Hi! My name is Sanjit Joseph and I'm a 3rd year CE major at Sixth. I'm from the Bay Area, so I've been surrounded by technology most of my life. I'm into building computers and I waste a lot of time (and money) messing with my PC and playing video games on it. I enjoy things outside of tech, though--as an Eagle Scout, I've done tons of backpacking throughout California and the US. I also hold a black belt in Shotokan Karate. As for this class, I'm pretty excited about all the different aspects of software engineering; frontend and backend both appeal to me, but I'm really just excited to work on a long class project in a team setting. - Hi! My name is Sanjit Joseph and I'm a 3rd year CE major at Sixth. I'm from the Bay Area, so I've been surrounded by technology most of my life. I'm into building computers and I waste a lot of time (and money) messing with my PC and playing video games on it. I enjoy things outside of tech, though--as an Eagle Scout, I've done tons of backpacking throughout California and the US. I also hold a black belt in Shotokan Karate. As for this class, I'm pretty excited about all the different aspects of software engineering; frontend and backend both appeal to me, but I'm really just excited to work on a long class project in a team setting.
- #### Link to Github: https://github.com/sm-joseph - #### Link to Github: https://github.com/sm-joseph
### **Isaac Otero** ### **Isaac Otero**
- #### About Me: - #### About Me:
- My name is Isaac Otero, I am a 5th year Cog Sci major. I am interested in front end development. I want to implement what I’ve learned from my design classes into my projects for front end development. - My name is Isaac Otero, I am a 5th year Cog Sci major. I am interested in front end development. I want to implement what I’ve learned from my design classes into my projects for front end development.
- #### Link to Github: https://github.com/Isaac-Otero - #### Link to Github: https://github.com/Isaac-Otero
### **Arthur Lu** ### **Arthur Lu**
- #### About Me: - #### About Me:
- My name is Arthur Lu and I am a 3rd year CE major. I am primarily interested in low level systems design, hardware development and optimization, and HPC architecture. I work as an undergraduate research assistant for Prof. Turakhia developing hardware accelerators for long length genome alignment. When I’m not busy, I like to relax with some retro video games. - My name is Arthur Lu and I am a 3rd year CE major. I am primarily interested in low level systems design, hardware development and optimization, and HPC architecture. I work as an undergraduate research assistant for Prof. Turakhia developing hardware accelerators for long length genome alignment. When I’m not busy, I like to relax with some retro video games.
- #### Link to Github: https://github.com/ltcptgeneral - #### Link to Github: https://github.com/ltcptgeneral

38
package.json
View File

@ -1,16 +1,22 @@
{ {
"name": "food-journal", "name": "food-journal",
"version": "1.0.0", "version": "1.0.0",
"scripts": { "scripts": {
"test": "mocha --recursive './{,!(node_modules)/**}/*.test.js'", "test": "mocha --recursive './{,!(node_modules)/**}/*.test.js'",
"lint": "eslint '**/*.js'", "lint": "eslint '**/*.js'",
"fix-style": "eslint --fix **/*.js" "fix-style": "eslint --fix **/*.js"
}, },
"html": { "html": {
"lintHTML": "npx htmlhint '**/*.html'", "lintHTML": "npx htmlhint '**/*.html'"
}, },
"devDependencies": { "css": {
"eslint": "^8.27.0", "lintCSS": "npx stylelint '**/*.css'"
"mocha": "10" },
} "devDependencies": {
} "eslint": "^8.27.0",
"mocha": "10",
"htmlhint": "1.1.4",
"stylelint": "14.14.1"
}
}

4
specs/adrs/README.md
View File

@ -1,2 +1,2 @@
# Overarching Decisions # Overarching Decisions
_We will eventually capture these as an ADR in markdown Links to an external site.(/specs/adrs will contain an individual document per major decision. There will be some initial ones that have to do with general project plan and approach, but more may be added as the project goes on. The main point of this capture is to explain why choices are made. As brainstorming may have your team settle on choices quickly capturing them in a document may be better than just mental consensus)_ _We will eventually capture these as an ADR in markdown Links to an external site.(/specs/adrs will contain an individual document per major decision. There will be some initial ones that have to do with general project plan and approach, but more may be added as the project goes on. The main point of this capture is to explain why choices are made. As brainstorming may have your team settle on choices quickly capturing them in a document may be better than just mental consensus)_

162
static/reset.css
View File

@ -1,82 +1,82 @@
/* This is a generic CSS file that sets preliminary rules for content that should be the same across pages */ /* This is a generic CSS file that sets preliminary rules for content that should be the same across pages */
html, body, div, span, object, iframe, html, body, div, span, object, iframe,
h1, h2, h3, h4, h5, h6, p, blockquote, pre, h1, h2, h3, h4, h5, h6, p, blockquote, pre,
abbr, address, cite, code, abbr, address, cite, code,
del, dfn, em, img, ins, kbd, q, samp, del, dfn, em, img, ins, kbd, q, samp,
small, strong, sub, sup, var, small, strong, sub, sup, var,
b, i, b, i,
dl, dt, dd, ol, ul, li, dl, dt, dd, ol, ul, li,
fieldset, form, label, legend, fieldset, form, label, legend,
table, caption, tbody, tfoot, thead, tr, th, td, table, caption, tbody, tfoot, thead, tr, th, td,
article, aside, canvas, details, figcaption, figure, article, aside, canvas, details, figcaption, figure,
footer, header, hgroup, menu, nav, section, summary, footer, header, hgroup, menu, nav, section, summary,
time, mark, audio, video { time, mark, audio, video {
margin: 0; margin: 0;
padding: 0; padding: 0;
border: 0; border: 0;
outline: 0; outline: 0;
font-size: 100%; font-size: 100%;
vertical-align: baseline; vertical-align: baseline;
background: transparent; background: transparent;
} }
body { body {
line-height: 1; line-height: 1;
} }
article,aside,details,figcaption,figure, article,aside,details,figcaption,figure,
footer,header,hgroup,menu,nav,section { footer,header,hgroup,menu,nav,section {
display: block; display: block;
} }
nav ul { nav ul {
list-style: none; list-style: none;
} }
blockquote, q { blockquote, q {
quotes: none; quotes: none;
} }
blockquote:before, blockquote:after, blockquote:before, blockquote:after,
q:before, q:after { q:before, q:after {
content: ''; content: '';
content: none; content: none;
} }
a { a {
margin: 0; margin: 0;
padding: 0; padding: 0;
font-size: 100%; font-size: 100%;
vertical-align: baseline; vertical-align: baseline;
background: transparent; background: transparent;
} }
table { table {
border-collapse: collapse; border-collapse: collapse;
border-spacing: 0; border-spacing: 0;
} }
input, select { input, select {
vertical-align :middle; vertical-align :middle;
} }
img, fieldset, object { img, fieldset, object {
border:none; border:none;
} }
*, *:after, *:before { *, *:after, *:before {
box-sizing:border-box; box-sizing:border-box;
} }
button, label { button, label {
cursor:pointer; cursor:pointer;
} }
html, body { html, body {
height:100%; height:100%;
} }
form { form {
border border
} }

54
testenv/testenv.js
View File

@ -1,28 +1,28 @@
module.exports = {environment}; module.exports = {environment};
function environment () { function environment () {
const localStorageMock = (function () { const localStorageMock = (function () {
let store = {}; let store = {};
return { return {
getItem(key) { getItem(key) {
return store[key]; return store[key];
}, },
setItem(key, value) { setItem(key, value) {
store[key] = value; store[key] = value;
}, },
clear() { clear() {
store = {}; store = {};
}, },
removeItem(key) { removeItem(key) {
delete store[key]; delete store[key];
}, },
getAll() { getAll() {
return store; return store;
}, },
}; };
})(); })();
let window = {}; let window = {};
Object.defineProperty(window, "localStorage", { value: localStorageMock }); Object.defineProperty(window, "localStorage", { value: localStorageMock });
return window; return window;
} }

160
testenv/testenv.test.js
View File

@ -1,81 +1,81 @@
const {environment} = require("./testenv.js"); const {environment} = require("./testenv.js");
var assert = require("assert"); var assert = require("assert");
var {describe, it, beforeEach} = require("mocha"); var {describe, it, beforeEach} = require("mocha");
var {saveToLocal, getFromLocal, removeFromLocal, clearLocal} = require("./testenv_helpers"); var {saveToLocal, getFromLocal, removeFromLocal, clearLocal} = require("./testenv_helpers");
beforeEach(() => { beforeEach(() => {
window = environment(); window = environment();
}); });
describe("test localStorage mock", () => { describe("test localStorage mock", () => {
it("test save and fetch", () => { it("test save and fetch", () => {
saveToLocal("testkey1", "testvalue1"); saveToLocal("testkey1", "testvalue1");
saveToLocal("testkey2", "testvalue2"); saveToLocal("testkey2", "testvalue2");
saveToLocal("testkey3", "testvalue3"); saveToLocal("testkey3", "testvalue3");
saveToLocal("testkey4", "testvalue4"); saveToLocal("testkey4", "testvalue4");
assert.equal(getFromLocal("testkey1"), "testvalue1"); assert.equal(getFromLocal("testkey1"), "testvalue1");
assert.equal(getFromLocal("testkey2"), "testvalue2"); assert.equal(getFromLocal("testkey2"), "testvalue2");
assert.equal(getFromLocal("testkey3"), "testvalue3"); assert.equal(getFromLocal("testkey3"), "testvalue3");
assert.equal(getFromLocal("testkey4"), "testvalue4"); assert.equal(getFromLocal("testkey4"), "testvalue4");
saveToLocal("testkey6", "testvalue5"); saveToLocal("testkey6", "testvalue5");
assert.equal(getFromLocal("testkey6"), "testvalue5"); assert.equal(getFromLocal("testkey6"), "testvalue5");
}); });
it("test window locality", () => { it("test window locality", () => {
assert.equal(getFromLocal("testkey1"), null); assert.equal(getFromLocal("testkey1"), null);
assert.equal(getFromLocal("testkey2"), null); assert.equal(getFromLocal("testkey2"), null);
assert.equal(getFromLocal("testkey3"), null); assert.equal(getFromLocal("testkey3"), null);
assert.equal(getFromLocal("testkey4"), null); assert.equal(getFromLocal("testkey4"), null);
}); });
it("test delete and fetch", () => { it("test delete and fetch", () => {
saveToLocal("testkey1", "testvalue1"); saveToLocal("testkey1", "testvalue1");
saveToLocal("testkey2", "testvalue2"); saveToLocal("testkey2", "testvalue2");
saveToLocal("testkey3", "testvalue3"); saveToLocal("testkey3", "testvalue3");
saveToLocal("testkey4", "testvalue4"); saveToLocal("testkey4", "testvalue4");
removeFromLocal("testkey3"); removeFromLocal("testkey3");
assert.equal(getFromLocal("testkey1"), "testvalue1"); assert.equal(getFromLocal("testkey1"), "testvalue1");
assert.equal(getFromLocal("testkey2"), "testvalue2"); assert.equal(getFromLocal("testkey2"), "testvalue2");
assert.equal(getFromLocal("testkey3"), null); assert.equal(getFromLocal("testkey3"), null);
assert.equal(getFromLocal("testkey4"), "testvalue4"); assert.equal(getFromLocal("testkey4"), "testvalue4");
removeFromLocal("testkey1"); removeFromLocal("testkey1");
assert.equal(getFromLocal("testkey1"), null); assert.equal(getFromLocal("testkey1"), null);
assert.equal(getFromLocal("testkey2"), "testvalue2"); assert.equal(getFromLocal("testkey2"), "testvalue2");
assert.equal(getFromLocal("testkey3"), null); assert.equal(getFromLocal("testkey3"), null);
assert.equal(getFromLocal("testkey4"), "testvalue4"); assert.equal(getFromLocal("testkey4"), "testvalue4");
removeFromLocal("testkey4"); removeFromLocal("testkey4");
assert.equal(getFromLocal("testkey1"), null); assert.equal(getFromLocal("testkey1"), null);
assert.equal(getFromLocal("testkey2"), "testvalue2"); assert.equal(getFromLocal("testkey2"), "testvalue2");
assert.equal(getFromLocal("testkey3"), null); assert.equal(getFromLocal("testkey3"), null);
assert.equal(getFromLocal("testkey4"), null); assert.equal(getFromLocal("testkey4"), null);
removeFromLocal("testkey2"); removeFromLocal("testkey2");
assert.equal(getFromLocal("testkey1"), null); assert.equal(getFromLocal("testkey1"), null);
assert.equal(getFromLocal("testkey2"), null); assert.equal(getFromLocal("testkey2"), null);
assert.equal(getFromLocal("testkey3"), null); assert.equal(getFromLocal("testkey3"), null);
assert.equal(getFromLocal("testkey4"), null); assert.equal(getFromLocal("testkey4"), null);
}); });
it("test clear and fetch", () => { it("test clear and fetch", () => {
saveToLocal("testkey1", "testvalue1"); saveToLocal("testkey1", "testvalue1");
saveToLocal("testkey2", "testvalue2"); saveToLocal("testkey2", "testvalue2");
saveToLocal("testkey3", "testvalue3"); saveToLocal("testkey3", "testvalue3");
saveToLocal("testkey4", "testvalue4"); saveToLocal("testkey4", "testvalue4");
clearLocal(); clearLocal();
assert.equal(getFromLocal("testkey1"), null); assert.equal(getFromLocal("testkey1"), null);
assert.equal(getFromLocal("testkey2"), null); assert.equal(getFromLocal("testkey2"), null);
assert.equal(getFromLocal("testkey3"), null); assert.equal(getFromLocal("testkey3"), null);
assert.equal(getFromLocal("testkey4"), null); assert.equal(getFromLocal("testkey4"), null);
}); });
}); });

32
testenv/testenv_helpers.js
View File

@ -1,17 +1,17 @@
module.exports = {saveToLocal, getFromLocal, removeFromLocal, clearLocal}; module.exports = {saveToLocal, getFromLocal, removeFromLocal, clearLocal};
function saveToLocal (k, v) { function saveToLocal (k, v) {
window.localStorage.setItem(k, v); window.localStorage.setItem(k, v);
} }
function getFromLocal (k) { function getFromLocal (k) {
return window.localStorage.getItem(k); return window.localStorage.getItem(k);
} }
function removeFromLocal (k) { function removeFromLocal (k) {
window.localStorage.removeItem(k); window.localStorage.removeItem(k);
} }
function clearLocal () { function clearLocal () {
window.localStorage.clear(); window.localStorage.clear();
} }