csesoc / degree-planner Goto Github PK

The Pathways MVP while works could use some CSS improvements such as changing the colour of the arrows based on the theme.

Searching courses in pathways and in plannify works by loading all 6000+ courses into a search component and filtering on the search options as the user loads input. For a dataset this large we need to move to a different implementation model in which the user types the course code and presses enter to yield the best result (by calling the backend and yielding such a result).

Now this change will mean no autocomplete in the current sense but will mean far better load times and performance overall.

There exists an incomplete Dockerfile to deploy it on the CSESoc provided servers, however it is not tested and probably not complete. Finishing one for development and production would be good to allow devs to more readily test it and to more readily deploy it.

As no Handbook API exists currently, scraping is the default method of yielding production data for this project. A scraper exists in partial completion; this needs to be completed so that we can populate our database with real data.

Specific requirements of scraping and data to be retrieved can be found in project spec.

To give the project a more unique feel, a theme should be created and implemented into the project including utilities to add a dark mode.

Try ZPEM8805:

Go to postman to query that course (localhost:3001/api/relations/ZPEM8805), there is no record of that course:

Pathways Cards were made to only show the code, name and a link to the course outline, however these cards can and should show far more information; so they should be updated to show as much information as possible such as UoC, when the course is running in the current year and whatever else possible.

We have API endpoints that interface with our database, we should provide frontend logic that calls these endpoints so that the frontend is using our actual data rather than temp data.