Opinionated quasar-framework starter kit - Part 2

Hi again!
Let's continue with this second part.

What's new?

---

https://github.com/gregory-latinier/quasar-starter-kit/pull/10 => Readme with install instructions

So a bit of documentation on how to start with this kit

---

https://github.com/gregory-latinier/quasar-starter-kit/pull/11 => Add api lint and fix errors

Like the web app has linting by default, linting needed to be added to the API package too. And of course there were some errors to fix...

---

https://github.com/gregory-latinier/quasar-starter-kit/pull/12 => Precommit hooks

The precommit hooks are here to be sure that we don't commit bad code in the first place and end up having commit like "Fixing errors", "Lint errors", "Fixing tests" ...
Right now, no unit or integration tests are implemented. The idea with those hooks is to run them too before doing any commit

---

https://github.com/gregory-latinier/quasar-starter-kit/pull/13 => Api validation

Before processing any requests, it's always good to be sure that we will handle validated data. This is the aim of this PR, providing the mean to be able to validate either a payload, the url params or url

---

https://github.com/gregory-latinier/quasar-starter-kit/pull/14 => User crud

This is getting real baby! Here is a simple CRUD example from the admin point of view with inline editing.

A classic user list

With inline editing to quickly update a mistake. There is no validation here for now.

And the basic user form

---

https://github.com/gregory-latinier/quasar-starter-kit/pull/15 => Auth endpoints

API endpoint shouldn't be accessible by everybody.
Authentication is now in place by default with the user scope. Meaning you need to be identified to use the API.
An endpoint should only be accessible by an admin? Just add auth: { access: { scope: 'admin' } } to the route options

---

https://github.com/gregory-latinier/quasar-starter-kit/pull/16 => Add form validation and new fields

API validation is good but UI validation is better. So let's add that!

This was done using only the quasar validation feature. Unfortunately this feature lacks the async validation and we can't test if the email is already taken using the backend for example. So either we need to add an external library or may be a quasar extension is coming soon? :D

---

https://github.com/gregory-latinier/quasar-starter-kit/pull/17 => Add login validation on both apps

It was just to put the validation feature on both login forms, in the client and admin app

---

https://github.com/gregory-latinier/quasar-starter-kit/commit/28f5de8b4131f1a20d89e926398b1742f799b4e2 => Add sample data and update Readme

Clearifying the sample data provided and give the user's password!

---

What's next?

There are a few improvements to be made but I think the third part will be the last. There are basic examples so that you're able to start your app if you like this starter kit

Stay tuned for the last part and don't forget our indiegogo campaign

---