Feat/Team Checkin Form routes, validators, controllers, and middlewar…

[tektaxi]

…e (#974)

• Create checkin form submit endpoint

• Finish hacker checkin form submit endpoint

• Change checkin form spreadsheet

• api route for checking in teams

• Add devpost and discord tag field validation

• Update db with devpost url

• Add url validation:

• added team checkin form status to settings

• remove workshops

• more validation

• test

• Updated email template dates and header logo

• Added hackboard role support

• Revert "Added hackboard role support"

This reverts commit 481d303.

• Feat/auto emails (Feat/auto emails #949)

• Update email templates with tentative dates

• Create service for sending automated status emails

• Created function to find hacker by their status

• API routing for automated emails

• Cleaner code

• API routing for getStatusCount function

• Added emails.js logic to middleware and controller files

• fixed authorization bug

• Added hackboard role support

• Revert "Added hackboard role support"

This reverts commit 481d303.

• update email dates

---

• Feat/create application review (Feat/create application review #944)

• not finished create app rev

• Reviewer status: 1/2 works (needs to enter twice??)

• Hacker Reviewer Feature

• Cleaner code

• remove uneccessary comments

• not finished create app rev

• Reviewer status: 1/2 works (needs to enter twice??)

• Hacker Reviewer Feature

• Cleaner code

• remove uneccessary comments

• not finished create app rev

• Reviewer status: 1/2 works (needs to enter twice??)

• Hacker Reviewer Feature

• Cleaner code

• remove uneccessary comments

• not finished create app rev

• Reviewer status: 1/2 works (needs to enter twice??)

• Hacker Reviewer Feature

• Cleaner code

• Fixed Application Error: implemented reviewers values from feat/review_filter and fixed the default value errors for reviewer status, name, and comments

• Fixed Application Error: implemented reviewers values from feat/review_filter and fixed the default value errors for reviewer status, name, and comments

• fixed authorization issues by adding all routes to routes.constant.js with unique IDs

• disable emails on status change by admin

---

• fixed merge issue with objectIDs

• Added hackboard role support (Added hackboard role support #955)

• Added hackboard role support

• minor edits to hackboard permissions

---

• Updated account invitation email content

• Feat/assign reviewers (Feat/assign reviewers #959)

• Assign 2 reviewers per unreviewed Hacker submitted before cutoff time. Will need a cleaning for documentation

• removed to requirement that the reviewer name has to be empty (now it's just filtering if hacker was created before cutoff)

• clean

• Use string[] parameter instead of hardcoded names

---

• Added script for sending interest form emails (Added script for sending interest form emails #954)

• Added script for sending interest form emails

• Usage comments

• quick fixes to assignReviewers (quick fixes to assignReviewers #961)

• quick fixes to assignreviewers

• fixed non existant fields conditional statements for assignReviewers

• need to fix: reviewer1 & 2 have same name

• fixed duplicate names

• cut off to dec 1 11:59 pm

• update cutoff

• date fix??

• add hacker id to team api response schema

• new acceptance email

• updated Marriott booking deadline

• round 2 acceptance email template

• updated rejection email

• updated wording

• added volunteer link

• added applied status to validateStatus function

• overrode email template to send declined emails to hackers with applied status (Fixed rejection email template bug #972)

• Finish hacker checkin form submit endpoint

• format sheet name

• remove checkin router dup

• fix

---

Tickets:

• HAC-

List of changes:

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• New release
• This change requires a documentation update

How has this been tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

Firmware version:
Hardware:
Toolchain:
SDK:

Questions for code reviewers?

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• Listed change(s) in the Changelog
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have made corresponding changes to the documentation
• Any dependent changes have been merged and published in downstream modules