The application duck should handle storing and manipulating application data, hence the name applications duck.
On load,
if the user is of type applicant, the GET request to /applications will return all of that users applications.
if the user if is of type executive, the GET request to /applications will return all of the current active applications. This is to be paginated and is currently out of scope.
The result is to be cached and stored in the store somewhere, for ease of access we store applications in an object of type { [id: number]: ApplicationObject }
The application duck should handle storing and manipulating application data, hence the name applications duck.
On load,
if the user is of type applicant, the
GET
request to/applications
will return all of that users applications.if the user if is of type executive, the
GET
request to/applications
will return all of the current active applications. This is to be paginated and is currently out of scope.The result is to be cached and stored in the store somewhere, for ease of access we store applications in an object of type
{ [id: number]: ApplicationObject }
Sample API response: