Skip to content

Swanky-Ibises/MasterMind

Repository files navigation

#MasterMind! Documentation v. 0.1.

MasterMind runs on a NERD tech stack: Node.js, Express, React, Database (in this case, mongoDB).

To start the application on a local machine:

  1. Run 'npm install'.
  2. Run 'npm install webpack -g'.
  3. Run 'webpack' on one terminal window, 'grunt start' on another, and mongoDB on a final terminal window.

End-Goal:

We envisioned a plethora of games that test mental capabilities, including but not limited to a memory card game, a word scramble game, maybe even a 'trick' game that forces the user to think 'outside the box'. The website will track the user's performance and give them a timeline showing how they've improved or not. The leaderboard will show the top 10 scores accross all users within a specific game as well as the current users highest score. Unless the game has a set number of attempts (say a 20 question test), ideally the game would have a timer on it that defines an end point when the score is calculated and submitted to the server.

Main Components and their purposes:

index.js: In order to provide the 'illusion' of multiple pages, react-router has to be implemented to direct react to render the proper component. This file contains all routes used to render and make available the proper html elements and the functions that interact with them.

config.js: The API used here is from https://market.mashape.com/wordsapi/wordsapi. You'll be able to generate your own wordsapi key and enter it in this file.

App.js: Currently renders the whole webpage through the navbar, which is the one constant element that should be rendered throughout the whole website. The state is currently not used, but is left there for future use.

NavBar.js: Contains a logout function and renders the other components when the proper link is clicked on.

SignUp.js: This component is a sign up form that makes posts requests to the server with data containing the username and password. Note: In order to keep the user logged in across components and also have persistent error messages that don't disappear after a re-render, we store the username and error messages in the local storage object. Upon a dismount, the error message local storage object is cleared but the local storage username persists.

Login.js: This component is a login form that is similar to the SignUp form in that it makes posts requests to the server with data containing the username and password. Note: In order to keep the user logged in across components and also have persistent error messages that don't disappear after a re-render, we store the username and error messages in the local storage object. Upon a dismount, the error message local storage object is cleared but the local storage username persists.

Back-End Components:

server/users/userModel.js: The schema in use by MongoDB is defined here. User scores are recorded in an array, with the highest scores of each game in their own property.

server/users/userController.js: All methods that interact directly with the database are defined in userController.js.

server/server.js: Handles all post/get requests and connections to the DB. Also determines what route is chosen when the user clicks on 'profile' page depending on whether or not they're logged in.

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published