My Solution
I have used the following Postgres connection string
postgresql://datacose:datacose@localhost:5432/datacose
As such, you will have to create a user datacose with the password datacose and give it access to a Postgres DB named datacose to get the project running.
I have used alembic to manage migrations. The migrations themselves contain the necessary table set up and seeding of data.
There is only one user
username: osama
password: Lahore22
I have already pre-populated the database (and the login form) with the user credentials.
I have used the @nuxtjs/auth-next to manage authentication. BootstrapVue, Vuetreeselect, Pydantic and SQLAlchemy have been used as instructed.
I have tried to implement as many features as possible. I might have missed a few minor things, however, I do feel that the code is sufficient to show my prowess.
DataCose Full Stack Challenge
The goal of this challenge if to create a Nuxt frontend with a FastAPI backend matching the objectives down below.
To bootstrap this project, we've used a basic Nuxt 2 and FastAPI template. There is a Dockerfile available in case you want to work with Docker during development, but this is not a requirement.
The usage of the following packages is mandatory:
- Nuxt
- BootstrapVue
- VueTreeselect (you need to install this yourself)
- FastAPI
- Pydantic
- SQLAlchemy (you need to install this yourself)
To store your data you can either use a sqllite database file, or use a local Postgres database (preferred).
If you choose to use a Postgres database, please provide a seed-file with some dummy data and a migration file to setup the database schema.
In case you use sqllite, provide the database file.
Objectives
Create a username/password protected app that authenticates API requests using Bearer tokens (not session tokens). Store the user credentials in your database and allow us to sign in using the frontend (please provide the credentials for one user, no need to create functionality to create users). All pages, except for the login page, should be inaccessible when not signed in.
Data schema
The portal will be used to manage data about authors and their books. An author can have zero or more books, a book always has an author. An author just has a required name field. Books have a required name field, and a required page numbers field.
Pages
In the portal, there should be two pages (+ a login page). Make sure a user can navigate to both pages using a nav-bar layout.
Authors
On this page, render a paginated table of authors with the following columns:
- Name
- Number of books (this is calculated based on the books)
On top of this page, add an input field that is used to search for authors. Next to it, create a button that opens a modal to add a new author. When clicked on a table row, show a modal to edit the author. Make sure any changes can be saved to the database.
The modal to add/edit an author should a name field (of the author) + a table with the books of the authors (name + number of pages). A user should be able to add, edit or delete a book.
Books
On this page, render a paginated table of books with the following columns:
- Name
- Author name
- Number of pages
On top of this page, add an input field that is used to search for books. Next to it, create a button that opens a modal to add a new book. When clicked on a table row, show a modal to edit the book. Make sure any changes can be saved to the database.
The modal to add/edit a book should have three fields:
- Name
- Number of pages
- Author (should be a searchable treeselect with authors)
Notes
The usage of the provided template is mandatory. Submissions not written in this template, will not be reviewed. Writing tests is not mandatory, but doing so will give you bonus points. Please fork this repository and invite info@datacose.com.