Connecting the GUI to the backend

We now have the first implementation of the GUI, with forms and even some logic associated with the authorization levels, but we do not yet have any data coming from the backend. This is what we are going to realize in the following sections. After adding authorization management to the backend, we will detail how the GUI will call the API to get some information and also focus on an important feature, pagination. This will be also the opportunity to think about the GUI in terms of autonomous components, which is as important as the separation of concerns in the API (which is the domain where we have mostly applied this principle, for now, even if it is a general principle that applies everywhere).

Modifying authorization in the backend

So far, we have connected the backend API to a client called BooksAPI. Not only does this name not make sense anymore, since we should also authorize the authors data referential service, but it is also more logical...