A core component of any web application is the endpoints required for communicating between the front-end and back-end, and for any user to access the website generally from a browser.
Given we are going forward with a Rust prototype and are using the Rocket web application framework, and other details discussed thus far at team meetings, our application will be built with a standard REST based API.
We should have endpoints for the following behavior (liable to change):
[x] user login
[x] user login submission
[x] get the current list of schedules/professors entered
[x] get the main page
[x] submit a new schedule/professor form(s)
These endpoints are necessary for mocking the current functionality of our application for sprint 1 features. No logic should actually be implemented within the context of this task.
Assignees
@ejmg
Background
Our application has a very minimal and straightforward UI [#5]. As such, our endpoints that are public facing will be limited and fairly simple.
Constraints and Assumptions
Functional Constraints:
Nothing dynamic yet, i.e. no JS should be considered nor necessary to handle this logic from the front to the back.
Backend is only taking empty inputs or dummy empty inputs in the requests.
Blockers
#1 and #2
6
15
Design Changes
This requires the implementation of our basic endpoints. The future design of the backend will be predicated/based off of this task's implemenation.
Implement basic REST endpoints
A core component of any web application is the endpoints required for communicating between the front-end and back-end, and for any user to access the website generally from a browser.
Given we are going forward with a Rust prototype and are using the Rocket web application framework, and other details discussed thus far at team meetings, our application will be built with a standard REST based API.
We should have endpoints for the following behavior (liable to change):
These endpoints are necessary for mocking the current functionality of our application for sprint 1 features. No logic should actually be implemented within the context of this task.
Assignees
@ejmg
Background
Our application has a very minimal and straightforward UI [#5]. As such, our endpoints that are public facing will be limited and fairly simple.
Constraints and Assumptions
Functional Constraints:
Blockers
#1 and #26
15
Design Changes
This requires the implementation of our basic endpoints. The future design of the backend will be predicated/based off of this task's implemenation.
References
None