ecrona / horse-bet Goto Github PK

Only re-render if needed, create smart shouldUpdate-logic in the overview component

Only render the component if the data has changed, new users, new fixtures or updated status / results

Redirect the user to the login page if not already authorized

Setup a firebase connection with ability to connect to dynamic firebase hosts

Write validation rules to communicate with the database

• User can fetch all users if authed
• User can fetch all fixtures if authed
• User can fetch own bets if authed, only limited bets from participants depending on deadline

Create an overview page, default landing page to begin with

Create a bet modal

• Make the bettable fixture cells clickable, open a bet modal when clicked on
• Display buttons for every bet choice
• Send a request when clicking one of the buttons, save the response in store
• Loader
• Handle errors with generic error messages
• Modal close button
• Highlight to the user if the deadline is passed

We should assume that request will be successful until they're not to make the app seem more responsive.

Create a poll that retrieves data on an appropriate interval

Create code foundation with vendors and a basic layout

• TypeScript + React
• Redux setup
• Solid directory hierarchy

Create an interface to add participants, sending out invitation links to participate

A timer displayed somewhere to siginify that the user has limited time to select bets

Connect the login component to Firebase Google Auth

The authenticated account needs to have an email that exists in the Firebase Database users document

Create the firebase database, model entities along with the database structure

Create some sort of migration system, or describe the database structure thoroughly

Work on an aesthetic layout with a green base color

Display a generic error message when authentication fails

We need a favico for branding

Look over simple deploy routines

Create a horse logo with a text, display it fashionably

Create a similar, smaller favico

The HMR does not retain the store, simply resets it

Initial view with login form

• Button to Google Authentication -> fake login
• Redirect to overview page on a successful login
• Loader

Create a README with thorough documentation

Create fixture table correlating fixtures to users

• Create selector function to merge relevant data to the view
• Render the fixture table, showing status icons / bet selection depending on data
• Divide fixtures in groups of event stages
• Display upcoming fixtures

An overview of the leading users

Display results by stage

Setup firebase google authentication and tie it to the login component

Only allow registration from a whitelist-like table (users) in the database

Create a firebase-function that can retrieve and store data in the api

• Reads from specified tournaments in the database
• Only attempts to fetch a tournament between start_date and end_date
• Create bridges to different API sources

The table cells shrink on mobile view