twilightcoders / card-games Goto Github PK

Remove the UI responsible for authentication from the starter app. We will leave the code in place (including the Prisma schema) in case we need to re-add this later, but for now, we are not authenticating this application, so we will scrap it.

ReactJS and Reactstrap are the natural choices to re-write this repo in

This portion of the game, is rendered in its own function. Rather than making this its own function, it should instead be its own component, with the necessary info sent through as props

The numeric input does not control correctly when being set to <input type='number'> whereas <input type='text'> controls itself just fine.

This is undesirable though, because we want a numeric keyboard on mobile. Will need to devise a solution.

This is mentioned in React issues here: facebook/react#6556

When the user is logged out, there is a 401 response code, with an error message of "JWT Expired" but when this happens the user is not logged out in a visual way

We don't necessarily have to rely on bootstrap class names to make this app look good...

• Material UI - this is actually listed as a dependency of mdbreact (I think?)
• Material Components
• React Toolbox
• (less likely) Materialize

There should be a moderator account type which can create custom game types, as well as edit existing game types. Additionally they can suspend user accounts.

Users should be able to register for an account with Google, and should sign in with that Google account

Decide on whether to use Rails, or Node, and whether to go serverless, or have a full stack.

User should be able to sign up with an email and log in with a magic link (no password)

There should be an admin role which can do everything aside from delete other admins. They should be able to promote users from a base user to a moderator, and from a moderator to another admin. They can also suspend any non-admin account

Due to a bug of Modal's within modal's in mdbreact, the inner modal cannot have a backdrop. Since the alert modal will sometimes be called from within a modal, and sometimes from the game itself (perhaps not, but regardless...) a prop should be passed to the alert modal to tell it whether or not it should display with a backdrop

Upgrade to Bootstrap 4

Configure Webpack 4, Relay, React, Babel, ESLint etc... from scratch without using create-react-app

How hard can that be? LOL

Perhaps explore working with Reach Router instead of React Router

Skin Bootstrap with a custom color scheme

If you add a collection of avatar's that you can select to use with a player's name, it might help the score keeper keep track of who's which score. This might be something to add near the end after testing, and all the core functions work.

The profile form should have validation for when there are errors, in addition there should be enforced (and displayed to the user) requirements for the account settings page.

The user should have the option to select from a list of predefined game types, or have an option to create a game type. Perhaps also in the future a new issue can be created which will allow that user to save the game type to their local storage for later use as well.

Use PropTypes validation to ensure that each game mode is checked and validated prior to trying to initialize a game.

There should be two environments for the supabase back end. One should be for development, the other should be for production