Initial commit

README.md

@@ -0,0 +1,55 @@
+# SDE - Full Stack - Technical Assessment
+
+As Software Development Engineers at EMIS;
+
+> We connect patients and healthcare professionals through integrated, ground-breaking technology, helping people live longer, healthier lives.
+
+## How can I demonstrate my technical ability?
+
+We'd like you to create a simple Single Page Application (SPA).
+
+The application should meet our [user driven requirements](/requirements/) and showcase your approach to software engineering.
+
+### Bonus
+
+To support your web application, we have provided a mock API.
+
+Replacing this mock API with an actual API would help demonstrate your skills across the full web stack. Your API can still use our [data/data.json](data/data.json) file as its datastore.
+
+## Where do I start?
+
+We have provided the following resources:
+
+- [/application](./application) - an base application generated using `npx create-react-app --template=typescript`
+- [/data](/data) - a [JSON Server](https://github.com/typicode/json-server) Mock API, which serves patient data. The Mock API serves the following endpoints:
+  - `GET /patients`
+  - `GET /patients/{id}`
+  - `POST /patients/{id}`
+  - `PATCH /patients/{id}`
+  - `DELETE /patients/{id}`
+
+Use these resources as a starting point for developing your application.
+
+## Do I need to use specific technologies?
+
+Your solution should use the following technology as it aligns well with our team and projects:
+
+- Single page application - Typescript, React
+- API (Bonus) - Typescript / Golang
+
+Beyond this, the world is your oyster! Go as far as you like!
+
+## How do I submit my solution?
+
+Create a public GitHub repository and push your solution including any documentation you feel necessary. Commit often - we would rather see a history of trial and error than a single monolithic commit. When you're finished, please send us the URL to the repository.
+
+We suggest you do not fork this repo, as your fork will be easily visible to other candidates.
+
+## What are you looking for in my solution?
+
+We will use the following criteria to assess your solutions:
+
+1. How effectively does the solution meet our user requirements?
+2. Is the solution engineered with a strong attention to detail?
+3. How does the solution implement open source software effectively?
+4. How does the solution ensure a high level of engineering quality?

application/.eslintrc.json

@@ -0,0 +1,23 @@
+{
+  "env": {
+    "browser": true,
+    "es2021": true
+  },
+  "extends": [
+    "eslint:recommended",
+    "plugin:react/recommended",
+    "plugin:@typescript-eslint/recommended"
+  ],
+  "parser": "@typescript-eslint/parser",
+  "parserOptions": {
+    "ecmaFeatures": {
+      "jsx": true
+    },
+    "ecmaVersion": 12,
+    "sourceType": "module"
+  },
+  "plugins": ["react", "@typescript-eslint"],
+  "rules": {
+    "@typescript-eslint/no-explicit-any": "off"
+  }
+}

application/.gitignore

@@ -0,0 +1,23 @@
+# See https://help.github.com/articles/ignoring-files/ for more about ignoring files.
+
+# dependencies
+/node_modules
+/.pnp
+.pnp.js
+
+# testing
+/coverage
+
+# production
+/build
+
+# misc
+.DS_Store
+.env.local
+.env.development.local
+.env.test.local
+.env.production.local
+
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*

application/README.md

@@ -0,0 +1,46 @@
+# Getting Started with Create React App
+
+This project was bootstrapped with [Create React App](https://github.com/facebook/create-react-app).
+
+## Available Scripts
+
+In the project directory, you can run:
+
+### `npm start`
+
+Runs the app in the development mode.\
+Open [http://localhost:3000](http://localhost:3000) to view it in the browser.
+
+The page will reload if you make edits.\
+You will also see any lint errors in the console.
+
+### `npm test`
+
+Launches the test runner in the interactive watch mode.\
+See the section about [running tests](https://facebook.github.io/create-react-app/docs/running-tests) for more information.
+
+### `npm run build`
+
+Builds the app for production to the `build` folder.\
+It correctly bundles React in production mode and optimizes the build for the best performance.
+
+The build is minified and the filenames include the hashes.\
+Your app is ready to be deployed!
+
+See the section about [deployment](https://facebook.github.io/create-react-app/docs/deployment) for more information.
+
+### `npm run eject`
+
+**Note: this is a one-way operation. Once you `eject`, you can’t go back!**
+
+If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project.
+
+Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
+
+You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.
+
+## Learn More
+
+You can learn more in the [Create React App documentation](https://facebook.github.io/create-react-app/docs/getting-started).
+
+To learn React, check out the [React documentation](https://reactjs.org/).