hergin / busshuttlemainrepository Goto Github PK

All of the models are exporting a class when they should be exporting an interface.

• Fake backend
• Real Backend

Tabbed Navigation Menu

• Main page
• • Autofill time
• • Stop
• • Boarded # with buttons
• • Left at stop # with buttons
• • Submit
• Sign in (driver, bus #)
• Settings
• • Manual Sync

We should investigate what needs to be updated for PHP 7.4 compatibility. Making sure everything still works.

There should be different levels of users in the system. Currently, the same username/password combo both authenticates to the dashboard and the driver app.

Actually, this user mess needs to be solved. I remember client wanted easy access for the drivers without any password etc. So they just select their names. We should clarify it with the client.

Brief description:
In the Desktop Interface source code, there are lines of code that are commented out/unused/ have too much white space.

In the class Stops.php on lines 153- 166 there is unnecessary white space.

Lines 45-48 has unnecessary white space as well.

Additional info:
link to Repository.

• Create method in component to get data from service
• Create a service that handles HttpClient requests
• • POST
• • GET (For populating Dropdowns)

Some functions did more than one thing, this should be reviewed to see if we can adhere more to the single responsibility principle.

• Background Sync API
• Service-Workers
• IndexedDB (workbox uses it to store requests offline)

Clean up code that was written in the admin desktop. For instance, get rid of some of the white space between lines and adjust indentation, try getting rid of some unnecessary code that may not be needed for the functions, and rewriting some comments so that they are more relevant to the code.

• Add Stops
• Delete Stops
• Update Stops

• Add Loops
• Delete Loops
• Update Loops

• Add Drivers
• Edit Drivers
• Update Drivers

It appears that google workbox will not work for our purposes with our current stack. We will have to discuss whether we want to implement a different solution in angular or move away from the framework scene and just try Javascript libraries like Vue.js, etc.

Originally posted by @kdesimini in #1 (comment)

We need to review our documents and make the changes to them that have been discussed.

Diagrams need to model the two Front-ends and Back-end that we've modified.

• Domain Model
• Class Diagram
• Requirements

• By Date
• By Loop
• By Stop
• By Driver

• Timestamp auto generated
• Date auto generated
• Will not reset 'driver', 'loop', 'route', etc when the form is submitted (ease of use)