fixed scanning and data processing (#105)

* renamed files and fixed first name not showing

* codacy readme + create clear store

* fix daily check in unaccessible

* fix camera

* create new utils

* checkin works completed

* complete registration

* fixed codacy

* fixed formatting

* readme codacy

Author: cweitat

Readme.md

@@ -75,39 +75,42 @@ Deployed in a production environment at [checkin.eventyay.com](https://checkin.e
 Only deployed locally with `npm run dev` or Netlify when you make a pull request it consumes the API exposed by development branch of open event server, hosted at [test-api.eventyay.com](https://test-api.eventyay.com).
 
 ## Further Reading / Useful Links
+[Vue.js](https://vuejs.org/)  
 
-- [Vue.js](https://vuejs.org/)
+[Vue Router](https://router.vuejs.org/)  
 
-- [Vue Router](https://router.vuejs.org/)
+[Pinia](https://pinia.vuejs.org/)  
 
-- [Pinia](https://pinia.vuejs.org/)
-  
-- [Tailwind CSS](https://tailwindcss.com/)
+[Tailwind CSS](https://tailwindcss.com/)  
 
-- [Headless UI](https://headlessui.com/)
+[Headless UI](https://headlessui.com/)  
 
-- [heroicons](https://heroicons.com/)
+[heroicons](https://heroicons.com/)  
 
-- [Vue Devtools for browsers](https://devtools.vuejs.org/guide/installation.html)
+[Vue Devtools for browsers](https://devtools.vuejs.org/guide/installation.html)
 
 
 ## Contributions Best Practices
 
 ### Commits
 
-- Write clear meaningful git commit messages (Do read [chris.beams.io/posts/git-commit/](https://chris.beams.io/posts/git-commit/))
-- Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (More info at [github.com/blog/1506-closing-issues-via-pull-requests](https://github.com/blog/1506-closing-issues-via-pull-requests) )
-- When you make very minor changes to a PR of yours (like for example fixing a failing Travis build or some small style corrections or minor changes requested by reviewers) make sure you squash your commits afterward so that you don't have an absurd number of commits for a very small fix. (Learn how to squash at [davidwalsh.name/squash-commits-git](https://davidwalsh.name/squash-commits-git) )
-- When you're submitting a PR for a UI-related issue, it would be really awesome if you add a screenshot of your change or a link to a deployment where it can be tested out along with your PR. It makes it very easy for the reviewers and you'll also get reviews quicker.
+Write clear meaningful git commit messages (Do read [https://chris.beams.io/posts/git-commit/](https://chris.beams.io/posts/git-commit/))  
+
+Make sure your PR's description contains GitHub's special keyword references that automatically close the related issue when the PR is merged. (More info at [https://github.com/blog/1506-closing-issues-via-pull-requests](https://github.com/blog/1506-closing-issues-via-pull-requests) )  
+
+When you make very minor changes to a PR of yours (like for example fixing a failing Travis build or some small style corrections or minor changes requested by reviewers) make sure you squash your commits afterward so that you don't have an absurd number of commits for a very small fix. (Learn how to squash at [https://davidwalsh.name/squash-commits-git](https://davidwalsh.name/squash-commits-git) )  
+
+When you're submitting a PR for a UI-related issue, it would be really awesome if you add a screenshot of your change or a link to a deployment where it can be tested out along with your PR. It makes it very easy for the reviewers and you'll also get reviews quicker.
 
 ### Feature Requests and Bug Reports
 
 When you file a feature request or when you are submitting a bug report to the [issue tracker](https://github.com/fossasia/open-event-checkin/issues), make sure you add steps to reproduce it.
 
 ### Join the development
 
-- Before you join development, please set up the project on your local machine, run it and go through the application completely.
-- If you would like to work on an issue, drop in a comment with the estimated completion date at the issue. If it is already assigned to someone, but there is no sign of any work being done, please feel free to drop in a comment.
+Before you join development, please set up the project on your local machine, run it and go through the application completely.  
+
+If you would like to work on an issue, drop in a comment with the estimated completion date at the issue. If it is already assigned to someone, but there is no sign of any work being done, please feel free to drop in a comment.
 
 ## License