Skip to content

repositive/frontend_exercise

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

18 Commits
 
 
 
 

Repository files navigation

React Frontend Exercise

Before you start coding

  • Preferable, create a public Git repository on Github or your Git hosting platform of choice, as long as it's accessible by us. We can also accept a ZIP file of the repository if you do not want to create an online repository. Please inlcude the .git folder so the history is retained.

  • Use create-react-app to create a React application skeleton on your development machine:

    npx create-react-app frontend_exercise_implementation
  • Work on your own and push commits regularly to your fork.

  • Once you are done provide running instructions! This is super important, if the code doesn't run, it's not done.

  • You do not need to do anything else, we can access your repository and review the results there. You have full control over the code, so please, do not remove your repository until we give you feedback!

The exercise

Below there is an image with the design of what you'll be building. We expect the exercise to take between one and two hours.

Design

The aim of this exercise is to create a histogram. The histogram represents a set of words and the number of occurrences of each word.

You will receive anbject in the following format:

{
  "title": 'Pets in Cambridge',
  "data": {
    "cat": 55,
    "dog": 14,
    "lizard": 37, // There are a lot of Liz lovers in Cambridge. :D
    "elephant": 3
  }
}

Notice that the elements of the data object are not sorted and that the amount of unique entities is unspecified and could range from 1 to ∞.

Create the histogram using the previous object meeting the criteria:

  • The histogram shows a given title
  • Each row consists of 3 elements:
    • The word
    • The number of occurances of the word
    • A bar representing the relative size of an element in the set.
  • The elements are sorted in descending order, so that the largest bar is on top.

Build first a minimal solution without taking into consideration the colour or the bars or other consmetic details.

Extensions

If you finish the main task and have some time left, there are some extra tasks below.

You don't need to pick the task in order, pick them as better suits your style and interests.

  • Add unit tests.
  • Create multiple histograms each histogram has a different base colour.
  • The colour of the bars should fade from dark to light, descending for the first five elements, the following elements use the color of the element in the fifth position.
  • Request the data from an API endpoit:
    • Design the API interface and write down the specification.
    • Mock the frontend requests to the API using such specification.

What we take into consideration:

Note that the order of the apearance of the items doesn't correlate with the importance with assign to them.

  • Testing, preferably TDD and with focus on failure instead of success cases.
  • Data manipulation strategies.
  • Code style, composition vs inheritance and oo vs functional methodologies
  • Treatment of logic vs state.
  • Understanding of DOM manipulation.
  • Understanding of CSS composition.
  • Legibility and maintainability of the code.
  • Understanding of async and how to deal with callback hells.
  • During testing, mocking methodologies and API faking strategies.
  • Version control management.

Releases

No releases published

Packages

No packages published