Where digital assets come to life

Frontend technical challenge

Introduction

Welcome to the Ledn frontend technical challenge! In this assessment, you'll embark on a unique journey that draws inspiration from the challenges our company has faced in the past and continues to address in the ever-evolving landscape of financial technology.

Our team has encountered scenarios that require a fine balance between technical prowess and creative problem-solving—qualities we believe define an exceptional frontend engineer. To make this experience both engaging and relevant, we've infused the challenge with a touch of creativity, drawing inspiration from an iconic theme.

While the scenario we present is influenced by the Star Wars universe, please note that this is merely a creative backdrop. You won't be navigating the galaxy far, far away, but rather addressing real challenges that our company has encountered or is currently grappling with.

Starting and submitting the application

1. Create a new private repository on your personal Github account.
2. Copy the content of Ledn challenge in your new private repository.
3. Install dependencies with npm install.
4. Start the application using npm start.
5. Open http://localhost:3000 in your browser to test the app.
6. Invite ledn-reviewer to your project once it is ready.
7. Email your contact at Ledn with a confirmation that ledn-reviewer has been added as a contributor and your project is ready for review.
8. Please include a screen capture of your solution, so we can assess whether there is differences between your environment and ours.

The challenge

Introduction

Welcome to the Coruscant Bank's engineering department. In a galaxy far, far away, following the fall of the Empire, the financial landscape is in disarray, and you, esteemed engineer, have been entrusted with a crucial mission.

You are now responsible for managing the financial affairs of high-net-worth clients in the tumultuous aftermath of the Empire's collapse. Your role is pivotal as you navigate through the remnants of the Imperial financial system to bring order to the chaos left in its wake.

As the chosen engineer, you have access to critical information:

• Clients: A roster of high-net-worth individuals whose fortunes are entwined with the fate of the galaxy.

• Planets: The vast array of planets where Coruscant Bank operates, each with its unique economic challenges and opportunities.

• Transactions: Detailed records of your clients' financial transactions, recorded in both the now obsolete "Imperial Crown Standard" and the widely accepted "Galactic Credit Standard".

• Exchange rates: The fluctuating exchange rates between the "Imperial Crown Standard" and the "Galactic Credit Standard", adding an extra layer of complexity to financial reconciliation.

In the wake of the Empire's fall, the Republic has turned to Coruscant Bank to aid in rectifying the administrative chaos left behind. Your mission is to build the foundation of the administrative application, which will eventually ensure the seamless transition of high-net-worth clients into the new era.

Requirements

Your task is to design the foundation of a user interface capable of identifying planets susceptible to uprisings and enabling proactive intervention. The objective is to build a software that assists administrators in analyzing transactions across various planets. To meet this goal, adhere to the following guidelines:

1. Transaction filtering:

   • For each planet, using all users' homeworld as a reference for transaction sources, filter transactions:
     • After a specified date.
     • With a status marked as inProgress.
     • Executed in the ICS ("Imperial Crown Standard") currency.

2. Planetary ranking:

   • From the transactions filtered previously, order the planets based on the total number of transactions, from the highest to the lowest.

3. Cumulative transaction values:

   • From the ordered list of planets, provide real-time cumulative values for all transactions in both ICS ("Imperial Crown Standard") and GCS ("Galactic Credit Standard") for each planet individually.

4. Security measures:

   • Implement a solution capable of turning all transactions with a status of inProgress for a given planet to blocked using a planet ID. This security measure is essential to prevent potential bad actors from exploiting the financial system and transferring funds to the Empire.

Technical requirements

To ensure the success of your mission, adhere to the following technical specifications:

• Data format:

  • Assume the date input for filtering transactions is from an HTML input.
  • Use only the planet ID to build the function that updates the transactions.

• Technologies & languages:

  • Use React Query to execute all the requests to the endpoints.
  • Build the solution using Typescript and React.

• Testing and validation:

  • Provide comprehensive guidelines for testing your data architecture.
  • Include step-by-step instructions for starting the solution.

Technical documentation

Backend data information

• ExchangeRate:

  • rate: Value of ICS in the GCS currency

• Planet:

  • id: Unique ID of the planet
  • residents: List of IDs belonging to users

• User:

  • id: Unique ID of the user
  • homeworld: ID of the homeworld of a user

• Transaction:

  • id: Unique transaction ID
  • user: ID of the user the transaction belongs to
  • amount: Amount of a given transaction
  • currency: Currency of the transaction (either ICS or GCS)
  • date: Date in ISO-8601 format
  • status: Status of the transaction which can be inProgress, completed or blocked

Swagger

PLANETS

Get all planets

• Endpoint: /api/planets
• Method: GET
• Description: Retrieve all planets.
• Response:

  {
  "planets": [
  {
    "name": "Planet 1",
    "rotation_period": "24",
    "orbital_period": "365",
    "diameter": "12742",
    "climate": "temperate",
    "gravity": "1",
    "terrain": "grasslands",
    "surface_water": "40",
    "population": "1000000000",
    "residents": [],
    "films": [],
    "created": "2024-01-18T12:00:00Z",
    "edited": "2024-01-18T12:00:00Z",
    "id": "1"
  },
  // ... other planets ...
  ]
  }

Get planet by ID

• Endpoint: /api/planets/:id
• Method: GET
• Description: Retrieve a planet by ID.
• Parameters:
  • id (path): ID of the planet.
• Response:

  {
  "name": "Planet 1",
  "rotation_period": "24",
  "orbital_period": "365",
  "diameter": "12742",
  "climate": "temperate",
  "gravity": "1",
  "terrain": "grasslands",
  "surface_water": "40",
  "population": "1000000000",
  "residents": [],
  "films": [],
  "created": "2024-01-18T12:00:00Z",
  "edited": "2024-01-18T12:00:00Z",
  "id": "1"
  }

USERS

Get all users

• Endpoint: /api/users
• Method: GET
• Description: Retrieve all users.
• Response:

  {
  "users": [
  {
    "name": "User 1",
    "height": "170",
    "mass": "70",
    // ... other user properties ...
    "id": "1"
  },
  // ... other users ...
  ]
  }

Get user by ID

• Endpoint: /api/users/:id
• Method: GET
• Description: Retrieve a user by ID.
• Parameters:
  • id (path): ID of the user.
• Response:

  {
  "name": "User 1",
  "height": "170",
  "mass": "70",
  // ... other user properties ...
  "id": "1"
  }

Get users by homeworld

• Endpoint: /api/users/planet/:planetId
• Method: GET
• Description: Retrieve users by homeworld.
• Parameters:
  • planetId (path): ID of the homeworld planet.
• Response:

  {
  "users": [
  {
    "name": "User 1",
    "height": "170",
    "mass": "70",
    // ... other user properties ...
    "id": "1"
  },
  // ... other users ...
  ]
  }

  TRANSACTIONS

  Get all transactions

• Endpoint: /api/transactions
• Method: GET
• Description: Retrieve all transactions.
• Response:

  {
  "transactions": [
  {
    "id": "1",
    "user": 1,
    "amount": 100,
    "currency": "GCS",
    "date": "2024-01-18T12:00:00Z"
  },
  // ... other transactions ...
  ]
  }

  Get transaction by ID

• Endpoint: /api/transactions/:id
• Method: GET
• Description: Retrieve a transaction by ID.
• Parameters:
  • id (path): ID of the transaction.
• Response:

  {
  "id": "1",
  "user": 1,
  "amount": 100,
  "currency": "GCS",
  "date": "2024-01-18T12:00:00Z"
  }

Get transactions by user ID

• Endpoint: /api/transactions/user/:userId
• Method: GET
• Description: Retrieve transactions by user ID.
• Parameters:
  • userId (path): ID of the user.
• Response:

  {
  "transactions": [
  {
    "id": "1",
    "user": 1,
    "amount": 100,
    "currency": "ICS",
    "date": "2024-01-18T12:00:00Z",
    "status": "inProgress"
  },
  // ... other transactions ...
  ]
  }

Get transactions for multiple user IDs

• Endpoint: /api/transactions/users/:userIds
• Method: GET
• Description: Retrieve transactions by user ID.
• Parameters:
  • userIds (path): ID of the user.
• Response:

  {
  "transactions": [
  {
    "id": "1",
    "user": 1,
    "amount": 100,
    "currency": "ICS",
    "date": "2024-01-18T12:00:00Z",
    "status": "inProgress"
  },
  // ... other transactions ...
  ]
  }

Update batch of transactions

• Endpoint: /api/transactions/update-batch

• Method: PUT

• Description: Update a batch of transactions at once.

• Request payload:

  {
  "transactions": [
  {
    "id": "1",
    "user": 1,
    "amount": 150,
    "currency": "USD",
    "date": "2024-01-18T12:00:00Z",
    "status": "processed"
  },
  // ... other transactions in the batch
  ]
  }

• Response:

  {
  "message": "Batch of transactions updated successfully"
  }

EXCHANGE RATE

Get exchange rate

• Endpoint: /api/exchange-rate
• Method: GET
• Description: Retrieve the current exchange rate between GCS and ICS. The rate is how many GCS (Galactic Credit Standard) it takes to amount to 1 ICS (Imperial Crown Standard)
• Response:

  {
  "rate": "1.123456"
  }