In this repository 02_your_code/
you will find the code corresponding to the solution of the following problem.
You can find more information about the api used in this project in 01_our_microservice/README.md
- React Js
- React Router Dom
- Redux Toolkit
- Sweet Alert
- Bootstrap
- Axios
View a live demo https://youtu.be/BzWAzE5ketM
Following features are posible thanks to the api used
- You can view all users registered
- You can filter the users in based of the message
- You can edit a user
- You can unsubscribe a user
- You can update a user
You need to clone https://github.com/edunext-hr/edunext-challenge-karvaroz.git
You will find more information about how to run the api in 01_our_microservice/README.md
.
Must run the 01_our_microservice before
cd 02_your_code
npm install
npm run dev
In this repository you will find the description and files of your personal coding challenge. The developer challenge is designed to give us an overview on your dexterity when developing front-end web applications based on React.
The main objective is to determine not only whether you have the technical knowledge, but also how you communicate the decisions you make along the way and how you work with existing code. We hope that you find this challenge motivating.
We are looking for someone who is a good fit for our team, and this requires that candidates alongside their code and technical skill are also motivated to work and to lead projects and features into completion, and that they are capable of communicating effectively with other members of the team and customers about the requirements, the specifications or the status of the work.
We will look at the results of this challenge through the lens of:
- Communication
- Clear
- Complete
- Independence of work
- Tech skills & best practices
- Correctness of the solution
- Architecture of the solution
- QA
- Code quality
- Unit testing
We want to evaluate you in a setting that is similar to our day to day work. For this, we ask you to download the code in this repository and make the customerdataapi
micro-service work. You will find more information about this service and how to run it in 01_our_microservice/README.md
.
Now, since you are applying for a frontend dev position we want to you to create an app from scratch that communicates with this service. The purpose and requirements of the app can be found in the file 02_your_code/RULES.md
To deliver your code, please make a Pull Request (PR) to the main
branch of the repository with your changes. The PR should include an explanation of the decisions you made.
We will look at the way you deliver the code, the quality of the code we give you in the microservice is the quality we expect. We encourage you to use equivalent or better tools to maintain it according to the best javascript standards that you know. We also look at the technical decisions and the explanation of your PR. The story this all tells us, lets us understand how you write software and how you work as part of a team.
As we said before, at eduNEXT we look at the code from many different angles. For this, we want to let you know of all the things that value and that we will look for when assessing your response.
- Organization of your code
- Clarity of your PR explanations or the questions in Campfire
- Code comments
- Iterative approach to development
- Using linting or other quality tools
You will receive extra points for special achievements in the resolution of the challenge.
- Adding unit tests to your code
- Using coverage measurements for your unit testing
- Using CI to run your quality processes
- More broadly, everything that demonstrates knowledge of modern software development practices
Please keep this challenge to yourself, we expect you to be the only author of the code that is published here.
-
Using conventional commits. https://www.conventionalcommits.org/en/v1.0.0/
-
Use comments in your code when you need to explain the intent of you code. https://blog.codinghorror.com/code-tells-you-how-comments-tell-you-why/
-
You can find a useful guide to make better commit messages here: https://chris.beams.io/posts/git-commit/.
-
Structuring your code like a champion: https://docs.python-guide.org/writing/structure/#structure-of-code-is-key
-
How to make a good Pull Request cover letter. https://blog.alphasmanifesto.com/2016/07/11/how-to-create-a-good-pull-request/
-
If you are using windows to run this, there are special instructions for you at
01_our_microservice/REAMDE.md