Background: The app is designed to use Google OAuth for authentication. This is the "sign in with Google" flow that you see all over the internet. "OAuth" is "Open Authentication Protocol" and it's an open standard, not anything Google-specific. When you see "Sign in with Facebook/Apple/etc" across the internet, those are OAuth flows as well, just using Facebook/Apple as the provider.

When you create an OAuth app with Google, you will get two strings: a "client ID" and a "client secret". These strings are used by the GauchoCourses app here: https://github.com/crunch-time/crunchtime/blob/main/backend/src/main/resources/application-prod.properties#L30-L33

Tasks:

A word of warning... it's probably best to do this using the club's Google account so the credentials can be passed down to future officers/members. If you use your personal account, then you'd have to give your password to the next cohort of students that work on this app!

• [x] Using club Google account, follow these instructions: https://developers.google.com/identity/sign-in/web/sign-in

You only need to do the numbered steps:

The wiki for the code is here: https://github.com/crunch-time/crunchtime/wiki. It contains info about contributing, how the repo is structured, setting up local dev environments, etc.

Let's copy those articles over to the Wiki for this repo: https://github.com/data-science-ucsb/gauchocourses/wiki

At the bottom of this page there's a not about configuring Jest to transpile files from node_modules. I added axios in there, since that was the import causing the issues

https://www.npmjs.com/package/@vue/cli-plugin-unit-jest

Removed conflicting dependencies that don't work on m1 chip. Updated node-sass to newer version. Works with the following npm and node versions:

npm mac: 8.19.2 npm windows: 8.15.0 node mac: v19.0.1 and v16.18.1 node windows: v16.17.1

Background: A common practice in modern software development is to run automated tests (unit tests, end-to-end tests) when a pull request is created against the main branch. This way the developer doesn't need to run them locally (or forget to run them locally) and it gives the team confidence that the changes in the PR won't break the app.

Task: Create a GitHub actions workflow that is triggered whenever a PR is created against the "main" branch. The steps inside the Docker container which run the tests (https://github.com/crunch-time/crunchtime/blob/main/Dockerfile#L8), so this will effectively run the frontend and backend unit tests.

The app will be hosted on Azure, so you'll need to create an Azure subscription using the club credit card,

• [x] Azure subscription is created: https://azure.microsoft.com/en-us/free/
  • [x] You'll probably want to create a Microsoft account for the club rather than a particular person, since this will be passed down
• [x] The PM's and DevOps people have created accounts on Azure
• [x] The PM's and DevOps people have been added to the Azure subscription: https://learn.microsoft.com/en-us/azure/role-based-access-control/role-assignments-portal-subscription-admin

Changes made:

• add gh action workflow file to build docker container to run tests
• changed the marven file to run node version 16 (changes apply to the docker container we create)

For a brief period @hallbrad and I were trying to make this project generic for other universities, but that's no longer the plan so this PR removes some of those genericizing commits and the application runs locally now... on my machine ;)

Resolves issue #16 but would like another pair of eyes to see if my changes are okay.

Also worked on the schedule padding issues from crunchtime https://github.com/crunch-time/crunchtime/issues/6

Still not an expert at Vue.js and the styling so would appreciate some code review to make sure anything else didn't break. Thanks!

Project running into multiple build errors on frontend

• [ ] Mutating props: https://eslint.vuejs.org/rules/no-mutating-props.html, https://dev.to/nop33/fixing-no-mutating-props-vue-error-with-v-model-54oh
• [ ] Multi word component names: https://eslint.vuejs.org/rules/multi-word-component-names.html
• [ ] Do not access Object.prototype method https://eslint.org/docs/latest/rules/no-prototype-builtins

Details in screenshot above.

The project was originally implemented ~3 years ago with Java 8. Java 8 is going to EOL soon, so we'll need to update this to Java 17.

Everyone on the team can download Java 17 here: https://learn.microsoft.com/en-us/java/openjdk/download

Tasks:

• [x] Update maven poms to reference Java 17
• [x] Update the Dockerfile to use Java 17
• [x] Update Maven dependencies, their current versions may not work with 17
• [ ] Ensure the application still builds and runs successfully

The application was written ~3 years ago with Node.js 12. The lates Node.js version as of writing is Node 16. You'll want to upgrade the frontend to use the latest Node.js version.

Some notes:

• The version of Node.js is specified here: https://github.com/data-science-ucsb/gauchocourses/blob/main/frontend/pom.xml#L33
• I removed two packages when trying to resurrect this project. You may want to ad these packages back: https://github.com/data-science-ucsb/gauchocourses/pull/10/commits/d40c56d633c1f5838a99c79b5600e11bb537d373

Tasks:

• [x] Update Node.js to a supported version
• [x] Update the packages in package.json to their supported versions
• [x] Ensure the application still builds and runs successfully