This app intends to keep a track on books and show what changes have occurred. To view the objective, go to the Objective section below.
It is generated using the Angular CLI v12 and therefore uses Angular 12. Some components from the Angular Material library are used as well.
In order to run this app, clone the repo and run npm install. After the installation of the required node modules completes, run npm run start. It should start and open in your default browser on localhost:4200.
This app uses sessionStorage to persist information about the books.
The first page that would show up is the screen where the changes would appear. It corresponds with All Changes. For convenience, a couple of mock changes are seeded when the app starts.
From the first page, one can toggle the switch buttons, enabling Filtering, Sorting, Grouping and Paging. By enabling a given data operation, an additional container with options is being shown.
The second page is All Books. It displays information about all the books. From there, one can change and delete entities.
To accomplish the data operations, a custom implementation of a table was used, namely <custom-table>. The datasource of the custom table would be taken through several pipes to eventually fulfil the data manipulations.
The data source is sessionStorage, as already mentioned, which is fetched by BooksService.
In order to edit the data, the app uses a FormGroup from @angular/forms.
A web front-end in Angular that displays the history of changes of book entities with pagination, filtering, ordering and optionally grouping.
The book entity should have
- An id
- A title
- A short description
- Publish date
- Authors
An example of changes could be a title was changed, an author was added, etc. In the list of changes, the app should display at least the time of change and a description of what was changed (e.g. Title was changed to “The Hobbit”)