https://github.com/maxkless/ticket-mgmt
https://github.com/maxkless/ticket-mgmt
Last synced: about 1 year ago
JSON representation
- Host: GitHub
- URL: https://github.com/maxkless/ticket-mgmt
- Owner: MaxKless
- Created: 2022-05-09T07:31:02.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2022-05-09T07:44:11.000Z (about 4 years ago)
- Last Synced: 2024-10-05T15:42:47.401Z (over 1 year ago)
- Language: TypeScript
- Size: 199 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Coding Assignment
The goal of this assignment is to showcase your ability to develop features and your coding style. Due to the time
constraint you will have to prioritize what you work on, and have to try and balance cleanliness with just getting it
done.
Even though the app is small, one can easily spend the whole week working on it: perfecting styles, testing every single
method, or carefully crafting every single line of code. Please don't! Do as much as you can in about two hours and
share the results.
The most important part of the interview will come after this one, when we look at the app together, talk about the
decisions you have made, etc..
## Getting Started
*Do not fork* this repo. Instead, use
the [Download ZIP](https://codeload.github.com/nrwl/nrwl-coding-assignment-angular/zip/refs/heads/main) link.
```bash
curl https://codeload.github.com/nrwl/nrwl-coding-assignment-angular/zip/refs/heads/main --output nrwl-coding-assignment-angular.zip
unzip nrwl-coding-assignment-angular.zip
cd nrwl-coding-assignment-angular-main
```
Then install the packages and you're good to go!
```bash
yarn
# run app
yarn start
# run tests
yarn test
```
## Ticketing managing application
Build a ticket managing app, where the user can add, filter, assign, and complete tickets.
* The app should have two screens: the list screen and the details screen. Please use the Angular router to manage the
transitions between them.
* Even though we tend to use NgRx for state management, you can use a different approach if you think it fits better.
* Write a couple of tests. The goal here is not to build a production-quality app, so don't test every single detail.
Two or three tests should be good enough.
* Don't forget about error handling and race conditions. The API server has a random delay. If you bump it up to say 10
seconds, would the app still work correctly?
## Submitting your solution
Please send us the link to your repo on GitHub, Gitlab, etc. We will continue to work on it during the pair-programming
sessions. Please also indicate approximately how long you spent on the submission.