You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Garrett Mills c81b778c4e
Add project demo video
4 years ago
Project_Demonstration Add project demo video 4 years ago
app Fix bad service import 4 years ago
config Comment all the things! 4 years ago
documentation Add other system documentation 4 years ago
frontend Finish writing tests for front-end 4 years ago
locale Comment all the things! 4 years ago
test updated the tests, uncertain about their effectiveness ATM 4 years ago
.gitignore Initial commit of framework 4 years ago Add dev setup instructions 4 years ago
LICENSE Initial commit of framework 4 years ago Add yarn run test command 4 years ago
Units.flitter.js Add logic for serving front-end from /app 4 years ago
example.env Flesh out Player model and write patch to populate players from sporting API 4 years ago
flaps.json Initial commit of framework 4 years ago
flitter Initial commit of framework 4 years ago
index.js Initial commit of framework 4 years ago
package.json Add yarn run test command 4 years ago
setup.js Comment all the things! 4 years ago
yarn.lock Start front end test example 4 years ago

Fantasy Football

EECS 448 - Project 4

Structure Info


This project has been wired up to use Vue.js to help organize components of the game.

These components are defined in files that end in the .component.js extension, and are located in the src/components/ directory.

The entry point for the project is the index.html. This file contains the basic logic for loading Vue, and adding the game board to the page.

Obviously, we'll flesh out the look-and-feel as we go along. This is just a basic starter for now.


This project uses the Flitter web framework for its API. The API is split into routes, controllers, and models.

The models interface with the database and represent different object-oriented structures in the game (players, teams, users, matchups, &c.)

The routes define which controller methods get called on which endpoints.

The controllers contain the logic for receiving requests and sending responses and will query the models for data.

There are also some .patch.js classes that contain logic for one-time data patches.

How to Run

First, install the dependencies:

  • Node.js 14.x or higher
  • The Yarn package manager
  • MongoDB
git clone app
cd app
yarn install

Set up the environment config by copying the template .env file and editing it to match the environment:

cp example.env .env
vim .env

Now, run the one time data patches like so:

node flitter shell
(flitter) ➤ await require('./setup')(_di)

This will pull in the latest NFL players and their stats and seed the database to get the game ready to play.

Now, start the server:

node index.js

Re-generating the documentation

To regenerate the docs, you need Node.js and the Yarn package manager installed. Then, just:

cd documentation

Running Tests

The tests are located in the test directory and are split into frontend and backend tests.

All tests are written expressively using the Mocha testing library.

After installing the Node dependencies, you can run the frontend and backend tests like so:

yarn run test

Works Cited


The files in the frontend/lib directory are external libraries used in this project.


The backend API uses the following technologies and external libraries:

  • Flitter
    • This is a free API which we use to pull in player stats and information from the NFL in the one-time data patches.
    • A free-trial account was used to populate the data for this app.
  • SkySilk
  • Other libraries
    • There are many other open-source libraries relied upon as sub-dependencies of the framework we used
    • These libraries and their licensure information can be found in the package.json file


  • Lucas Brakenridge
  • Javier Barea Lara
  • Garrett Mills
  • Evan Powell
  • Alec Horlick-Mills