Create user signup to get notified about map details

[lightableMatch]

Start with WHY?

Why do we need to do work? (Who is requesting this work?) I want to create a user signup for notifications to gain some knowledge about user account development stuff. This also would be a useful feature for users. This issue is intended to notify users when their specified map + game mode combination will be up next in rotation. To give it meaning it will be used to notify via email or something users about whether a certain map is in rotation or if maps have just rotated or if there is a new ranked season or something.

What is the issue? What needs to be resolved?

• AS A Web developer
• I WANT user notification feature
• SO THAT users will know when certain maps will be up

Acceptance Criteria

• GIVEN a user signs up for map notifications
• WHEN the selected map for notifications is next in rotation
• THEN the user will get an email that the map is next in rotation.

Any other notes / resources to share?

-Look into a form endpoint for users to submit a notification stub -Look into validating for duplicate emails and confirming notification submissions -Look into an email sender

[lightableMatch]

Progress: 1f9bd0c917b93199ed2a725da1a149cb743ed906

• Created an endpoint for user sign up which can be accessed via a button on the footer
• Modularized the footer and nav html components for each endpoint to point to a single place

[lightableMatch]

Progress: 2dff8a202a48ec04c6063c488916d98ac0ade67e

• Worked on architecting data object/mapping for DB

[lightableMatch]

Progress: 677bb80bf9e472f5bea5cc328d2ebbef36c4dd2c

• Created forms for user signup

[lightableMatch]

Progress: 52cb65670f8e3f97484fa2ba8d7d680282425e96

• Able to pass user data from view --> controller
• Also added enums for gamemodes and maps that will probably never be used
• Added confirmation page when user submits data
• Problem: If user reloads page data gets resubmitted since it is in the url

[lightableMatch]

Progress: 89c4a5966ce7ab34abcce75c4dbe942754669109 Not meant for this issue but was done on userSignup branch

• Cleaned map page headers
• Added timer to competitive since they added that to their api

[lightableMatch]

Progress: 014f851ab1b469f9d495de17f6a75182258011d5

• Not related but for some reason it was a maven build wrapped in a gradle build, I must've done some funky stuff when trying to build the application.

[lightableMatch]

Progress: 0b91f78b96b06bffcb5b53163e723da63616d77d

• Synced laptop up to remote branch
• Added laptop changes to remote branch
• • Added day timer to countdown
• • Added yml file for database config

[lightableMatch]

Getting back into the notification feature

Progress: bd91ff6f277941d175e14b43f62c39c2db8ce317

• Creating enum values for map and gamemode
• This will make it easier(and harder) to communicate map data across service

[lightableMatch]

Progress: ddeea84e89de46a6bd2c2dea1b870b416b21e164

• Fleshed out enum data and brought it up to html via controller

[lightableMatch]

Progress: daa59ff9618d92c344aef5b94010ea7493094ed7

• Bind enum to checkbox input data

[lightableMatch]

Progress: 601e8522cfbc64f19d31c7966235599bdace32fd

• Separating map values to different game modes.

[lightableMatch]

Progress: 0ef81801881a34dbb486099a25c85e0560768018

• Not gonna get into it but progress to the form

[lightableMatch]

Progress: 53cfafe619059c70cd6d146722092629d81537d8

• Implemented new structure for notification form that works well!
• Now it is time to start working on the backend of this feature
• The design of the frontend could still be improved upon

[lightableMatch]

Progress: 6d80d5d97cf26e51cf874587e96a89ee4e1d6afc

• Notification objects can now be persisted

[lightableMatch]

Progress: 457ee8d22345d14b84341c9751309ed7a07c577f, a894613202705cf2c62ba871b4bf3f22abd0a0d5, 8c1be1f49e40437783647dbfbb6565fdb0b3ac81

-All commits relate to work on html of notification page

[lightableMatch]

Second Half of Issue: Notifying Users when their maps are live.

Currently users can post their emails and the map + gamemode combinations they would like to be notified about. This data then gets persisted in a database. The new objective is made of two main parts:

• Logic to see which users should be notified when maps get updated
• Once the users are identified an emailing service that sends out an email notifying them

[lightableMatch]

Progress: ba8417f8c2e5ae41719a4b208867f458631a0284

The second half of issue is practically completed but no polished. Remaining work to be done:

• Condense notification pages to a single endpoint
• Have better error handling if email does not exist in the application for deletion

I will be merging to master at this point and leaving this work as secondary issues to be completed at my own convenience.