Front End Challenge Solution (Thanos Kaloudis)

.browserslistrc

@@ -0,0 +1,3 @@
+> 1%
+last 2 versions
+not dead

.eslintrc.js

@@ -0,0 +1,29 @@
+module.exports = {
+  root: true,
+  env: {
+    node: true
+  },
+  'extends': [
+    'plugin:vue/vue3-essential',
+    'eslint:recommended',
+    '@vue/typescript/recommended'
+  ],
+  parserOptions: {
+    ecmaVersion: 2020
+  },
+  rules: {
+    'no-console': process.env.NODE_ENV === 'production' ? 'warn' : 'off',
+    'no-debugger': process.env.NODE_ENV === 'production' ? 'warn' : 'off'
+  },
+  overrides: [
+    {
+      files: [
+        '**/__tests__/*.{j,t}s?(x)',
+        '**/tests/unit/**/*.spec.{j,t}s?(x)'
+      ],
+      env: {
+        jest: true
+      }
+    }
+  ]
+}

.gitignore

@@ -0,0 +1,23 @@
+.DS_Store
+node_modules
+/dist
+
+
+# local env files
+.env.local
+.env.*.local
+
+# Log files
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+
+# Editor directories and files
+.idea
+.vscode
+*.suo
+*.ntvs*
+*.njsproj
+*.sln
+*.sw?

README.md

@@ -1,79 +1,33 @@
-# Frontend Challenge
+# Transcriptions App
 
-Our goal is to understand:
-- How knowledgeable you are
-- How well you structure your app
-- How well can you visually reproduce a mockup
+## Description
+This project has been made using Vue 3 and TypeScript 
 
-Some restrictions:
-- Use the Vue javascript framework and its Component system
-- Don't use a UI framework like Bootstrap
+## Set up
+1. Make sure Node and npm are installed from the terminal. Steps:
 
-Your challenge will consist of the following:
+    ```
+    npm install
+    ```
 
-You'll have to build a small web app that is able to **fetch data** from an endpoint we provide, **list the data** from the endpoint, allow **editing the data**, **adding and removing** rows, and then **pushing the data** to another endpoint.
+2. Start the project.
 
-Please fork this repo and commit your changes to the fork.
+    ```
+    npm run serve
+    ```
 
-Here is a preview of what we are expecting:
+3. Now you can visit http://localhost:8080 to view the client
 
-![Sample](_README_assets/sample.png)
+4. To run the Tests: 
 
-Keep in mind that we may ask you about some of the decisions you made while building the app.
+    ```
+    npm run test:unit
+    ```
 
-## Important information to complete the challenge
+## Notes
 
-### Data source
+* Data used from Mock API (http://www.mocky.io/v2/5ae1c5792d00004d009d7e5c)
 
-Fetch the data from this endpoint [http://www.mocky.io/v2/5ae1c5792d00004d009d7e5c](http://www.mocky.io/v2/5ae1c5792d00004d009d7e5c)
 
-Using Mocky should produce no cross origin errors and should work fine for this challenge. If you do find issues, it's OK to copy the JSON into your preferred method to then provide the data to the app.
 
-### Assets, measurements, and other details
-
-Inside this repository you'll find a folder named `assets-for-challenge`. Inside this folder you can find all the icons we expect you to use, in multiple formats, use what you think is best.
-
-## Detailed comments on each element
-
-![Elements Numbered](_README_assets/challenge-elements-numbered.png)
-
-**Functionality**
-
-The app should let the user do the following:
-
-- **1** - _Get data_ button. When the user **clicks on this button**, your app will **get the data from the URL** in [Data source](#Data source) and fill the list
-- **2** - _Upload data_ button. When the user **clicks on this button**, your app will **make a POST request to the same url** as the _Get data_ button. You should send the latest information on the list using the same structure as you have received it.
-- **3** - _Custom checkbox_. When the user **clicks on the checkbox**, it will become checked. It will not have any other functionality.
-- **4** - _Add line_ button. When the user **clicks on this button**, a **new row will be added to the list** and the user should be able to **write text in both fields**.
-- **5** - _Delete row_ button. This button should be **visible only when hovering** each row item. When the user **clicks on this button**, your app will **remove that row** from the list.
-- **6** - List _item title_ **This title should be editable**.
-- **7** - List _item content_. **This content should be editable**.
-- **8** - _App title_. No functionality.
-- **9** - _Person icon_ linked to each row. No functionality.
-
-Notes:
-
-- Don't worry about the blank state before loading the content.
-
-**Style Attributes**
-
-These are some and useful details about some of the elements
-
-- **3** - The checkbox is 16px wide and 16px high. The purple color is `#859EFF`
-- **6** - The font-family of the _item title_ is `Montserrat`, the weight is `SemiBold`, the size is `16px`, and the color is `#566074`
-- **7** - The font-family of the _item content_ is `Open Sans`, the weight is `Regular`, the size is `16px`, and the color is `#778195`
-- **8** - The font-family of the _app title_ is `Montserrat`, the weight is `Medium`, the size is `18px`, and the color is `#414C5E`
-
-The data above is enough to complete challenge. We also include the source Sketch file in the repository, in case you want to check the original file. You can find it in `_README_assets/Challenge.sketch`
-
-## Typography
-
-- You can find [Montserrat on Google Fonts](https://fonts.google.com/specimen/Montserrat)
-- You can find [Open Sans on Google Fonts](https://fonts.google.com/specimen/Open+Sans)
-
-## Bonus points:
-
-- Keeping in mind accessibility
-- Adding tests to your components and app
-- Using a store (Vuex) to manage the application data
-- Using vue-router to prepare the app for a future where it would have multiple routes
+

babel.config.js

@@ -0,0 +1,5 @@
+module.exports = {
+  presets: [
+    '@vue/cli-plugin-babel/preset'
+  ]
+}

jest.config.js

@@ -0,0 +1,6 @@
+module.exports = {
+  preset: '@vue/cli-plugin-unit-jest/presets/typescript-and-babel',
+  transform: {
+    '^.+\\.vue$': 'vue-jest'
+  }
+}