React - Basics

What you'll learn?

Description: You can use basic features of the framework, that allows you to deliver the most common features.

Person who successfully completed requirement for given block can:

  • Can deliver simple, typical functionalities with little to no additional help
  • When asking for help, can present the problem and already explored solutions clearly and in detail
  • Can debug simple problems within the application (excluding framework) using the right tooling
  • Can use Redux and related tools
  • Is capable of leveraging the most commonly used React capabilities
  • Has working knowledge of the most commonly used packages/libraries

Areas

React / Overview
0 questions • 0 katas
After this section, you will know what is React and what it’s used for.

Learn

Interview

React / JSX
0 questions • 0 katas
After this section, you will know how to use JSX, how it differs from HTML and how to use ClassNames package.

Learn

Interview

Katas

React / Hooks
0 questions • 0 katas
After this section, you will know commonly used React hooks and React-Use package.

Learn

Interview

Katas

React / Performance
0 questions • 0 katas
After this section, you will know how to prevent common mistakes degrading React performance.

Learn

Interview

Katas

React / Devtools
0 questions • 0 katas
After this section, you will know how to effectively use React Development tools.

Learn

Katas

React / Routing
0 questions • 0 katas
After this section, you will know how to implement routing in React SPA application.

Learn

Interview

Katas

React / Forms
0 questions • 0 katas
After this section, you will know how to create basic forms and validate user input.

Learn

Interview

Katas

React / Testing
0 questions • 0 katas
After this section, you will know how to test React application.

Learn

Interview

Katas

State management
0 questions • 0 katas
After this section, you will know what is Client and Server State and what challenges it presents.

Learn

  • 📗 8 ways to handle Client State
  • 📗 Server state challenges
  • 📗 Server vs Client state
    • Server state
      • backend is the source of truth,
      • data can get out of sync, can be changed by another user/process without frontend knowing about it
      • is async, so we need to track stages/progress of the requests
      • it requires refetching the data in the background to display fresh state
      • allow for easy tracking of request status and resetting,
      • server state requires keeping the data on the app and on the server in sync (as much as possible) handle errors by refetching the data, preventing fetching the same data twice
    • Client state
      • originates from the user interaction, and exist only for this user
      • can be synchronous
      • full control and knowledge about state
      • client state needs store and load data to localstorage for persistence

Interview

Server State management / Usage
0 questions • 0 katas
After this section, you will know how to implement basic features for Server State.

Learn

Interview

Katas

Server State management / Devtools
0 questions • 0 katas
After this section, you will know how to use devtools for preferred Server State management package.

Learn

Katas

Global Client State management / Usage
0 questions • 0 katas
After this section, you will know how to manage Global Client State.

Learn

Interview

Katas