HOW TO USE:
- The Web Page can be found at the following link: https://ecse321-group7-web.herokuapp.com/#/
- The first time it is opened, it may take a few seconds for the data to populate on the page
- In addition, to be completely clear the filtering statuses mean the following:
- En Route - The specific trip is currently in progress (has not reached final destination)
- Active - The user (passenger) has been on at least one trip
- All - displays all users in the database
NOTE:
- Changes were also made to the backend as part of this Sprint 3, more details at the backend repository
- Repository Link: https://github.com/ECSE321-Fall2018/t07
Nov. 22, 2018: (Frontend)
- Minor changes to wording and text presentation across the different views of the web page
- Minor changes to UI (button, checkmark/crossmark instead of "true/false")
- Add loading spinner
Nov. 19, 2018: (Frontend)
- Minor typo fixes to some of the text
- Formatting changes to text such that names and locations are displayed with capitalized first letters
- Display of the destinations was also altered to remove the brackets and quotes
- Searching implemented for fleet status
- Filtering active/inactive trips, drivers and passengers implemented for fleet status
- Filtering by date implemented for ranking
- Backend bugfix and new feature (see backend commit upto 4e83cc0)
Nov. 18, 2018: (Backend)
- Additional changes were made to the backend repository (linked below)
- REST endpoints were added to support the ranking feature (for drivers, passengers and trips)
- Ranking is done by counting number of trips a driver or passenger was on, or the number of occurrences of a certain route for trip ranking
- All 3 of the added endpoints support parameters for startDate and endDate that bound the search
- See the other repository for full details
(Frontend)
- Implemented all basic components, fleet data & rankings. --- but still missing filtering and searching
- Setup for Heroku (don't forget "npm run build" before deploying to Heroku) --- Importing 'Express' and setting up server.js in the root --- Modifying the HTTPRequest so that it goes through HTTPS
Nov. 17, 2018 (Backend)
- Changes were made to the backend repository (https://github.com/ECSE321-Fall2018/t07)
- REST endpoints were added to support the partial matching search functions for passengers, drivers and trips
- These search endpoints also support status modifiers so you can search for every result, only those that have been on trips or those that are on in progress trips
- See the other repository for full details (Frontend)
- Bootstrap template installed
- Router setup for /
- Still not sure why Heroku doesn't recognize this code: procfile?
npm install
npm run serve
npm run build
npm run test
npm run lint
npm run test:e2e
npm run test:unit