Design Systems & Component Libraries · Leçon

Props, état et gestion des événements

Maîtrisez le transfert de données, la gestion de l’état interne et la prise en charge efficace des interactions utilisateur au sein de vos composants.

Props, état et gestion des événements est une leçon Design Systems & Component Libraries gratuite sur CoddyKit. Ceci est la leçon 2 sur 4. Tu peux lire la leçon complète ci-dessous gratuitement — puis la pratiquer en direct dans le navigateur avec un éditeur de code intégré et un tuteur IA 24/7. Elle fait partie du parcours d'apprentissage Design Systems & Component Libraries, et ta progression se synchronise sur le web et l'application CoddyKit. Le cours Design Systems & Component Libraries comprend 4 leçons au total.

Certaines parties de cette leçon n'ont pas encore été traduites et s'affichent en anglais.

Data Flow in Components

Components are the building blocks of UIs. To make them dynamic and interactive, we need ways for them to receive data, manage their own internal information, and react to user actions.

This lesson explores three fundamental concepts: Props, State, and Event Handling. Mastering these allows you to create truly reusable and responsive UI components.

Props: Component Inputs

Props (short for "properties") are how components receive data from their parent components. Think of them like arguments you pass to a function.

They are immutable: a component should never modify its own props.
They enable parent-to-child communication.
They make components reusable by allowing different data inputs.

Passing Data with Props

Here's a simplified example. We'll create a GreetingComponent that takes a name as a prop and displays it. Notice how name is provided when the component is created.

class GreetingComponent {
    private String name; // This acts like a 'prop'

    public GreetingComponent(String name) {
        this.name = name;
    }

    public void render() {
        System.out.println("Hello, " + name + "!");
    }
}

public class Main {
    public static void main(String[] args) {
        // Create a component and pass a 'name' prop
        GreetingComponent userGreeting = new GreetingComponent("Alice");
        userGreeting.render();

        GreetingComponent guestGreeting = new GreetingComponent("Guest");
        guestGreeting.render();
    }
}

Props are Read-Only

A crucial rule for props is that they are read-only. Once a component receives props, it should not try to change them directly.

Why? This ensures predictable behavior, makes debugging easier, and prevents unexpected side effects in other parts of your application. If data needs to change, it should be managed by state (which we'll cover next).

State: Internal, Mutable Data

While props are external inputs, state is a component's own internal data that it manages and can change over time. Think of it as the component's private memory.

It's mutable: components can update their own state.
It controls dynamic behavior and changes in the UI.
Updates to state typically trigger a re-render of the component.

State in Action: A Counter

Let's simulate a simple CounterComponent. It will keep track of a number internally (its state) and have a method to increment that number. Each increment changes its internal state and "re-renders" its display.

class CounterComponent {
    private int count; // This is the component's internal 'state'

    public CounterComponent(int initialCount) {
        this.count = initialCount;
    }

    public void increment() {
        System.out.println("Incrementing...");
        this.count++; // Modifying internal state
        render(); // Simulate re-rendering after state change
    }

    public void render() {
        System.out.println("Current Count: " + count);
    }
}

public class Main {
    public static void main(String[] args) {
        CounterComponent myCounter = new CounterComponent(0);
        myCounter.render(); // Initial display: 0

        myCounter.increment(); // Count becomes 1
        myCounter.increment(); // Count becomes 2
    }
}

Props vs. State: The Distinction

Choosing between props and state can be tricky for beginners. Here's a simple rule:

Use Props: For data passed down from a parent component, or for data that doesn't change within the component itself.
Use State: For data that is managed internally by the component and is expected to change based on user interactions or other events.

If a component needs to change its own data, it needs state. If it just needs to display data given to it, props are sufficient.

Event Handling: Responding to Users

Event handling is how your components react to user interactions, like clicks, key presses, or input changes. When an event occurs, an "event handler" function is triggered.

Event handlers are often used to update a component's state, which then causes the UI to reflect the new data.

Event Handling & State Updates

Let's extend our counter example. We'll simulate a Button that, when "clicked", triggers our CounterComponent to increment its state. This shows how user actions (events) drive state changes.

interface ClickListener { // Simulates an event listener
    void onClick();
}

class Button {
    private String label;
    private ClickListener listener;

    public Button(String label, ClickListener listener) {
        this.label = label;
        this.listener = listener;
    }

    public void simulateClick() {
        System.out.println("Button '" + label + "' was pressed!");
        if (listener != null) {
            listener.onClick(); // Triggers the listener
        }
    }
}

class InteractiveCounter implements ClickListener {
    private int count; // State

    public InteractiveCounter(int initialCount) {
        this.count = initialCount;
    }

    @Override
    public void onClick() { // This is our event handler
        System.out.println("Event received! Updating state...");
        this.count++; // Update state
        render();
    }

    public void render() {
        System.out.println("Displaying Count: " + count);
    }
}

public class Main {
    public static void main(String[] args) {
        InteractiveCounter app = new InteractiveCounter(0);
        app.render(); // Initial display

        // Create a button and link its click event to our counter's handler
        Button incrementBtn = new Button("Increment", app);

        incrementBtn.simulateClick(); // Simulate user click 1
        incrementBtn.simulateClick(); // Simulate user click 2
    }
}

Quick Check: Data Flow

Consider a component that displays a user's profile picture and name. The user can also click a button to "like" the profile, and the like count updates instantly.

Which part of this component would typically be managed by props, and which by state?

Recap: Props, State & Events

Great job! You've learned the core concepts of building interactive UI components:

Props: External, read-only data passed into a component.
State: Internal, mutable data managed by a component, causing re-renders when changed.
Event Handling: Functions that respond to user interactions, often updating state.

These concepts are fundamental to creating dynamic and responsive user interfaces. Keep practicing!

Questions Fréquemment Posées

La leçon « Props, état et gestion des événements » est-elle gratuite ?

Oui — le texte complet de « Props, état et gestion des événements » est gratuit à lire ici sur le web. Pour la pratiquer de manière interactive (un éditeur de code intégré et un tuteur IA 24/7) et déverrouiller le reste du cours Design Systems & Component Libraries, passe à CoddyKit PRO. Le cours Design Systems & Component Libraries comprend 4 leçons au total.

Qu'est-ce que j'apprendrai dans « Props, état et gestion des événements » ?

Maîtrisez le transfert de données, la gestion de l’état interne et la prise en charge efficace des interactions utilisateur au sein de vos composants. Tu pratiques Design Systems & Component Libraries avec du code pratique que tu exécutes directement dans le navigateur, et un tuteur IA 24/7 répond à tes questions au fur et à mesure que tu avances dans la leçon.

Dois-je avoir de l'expérience pour commencer Design Systems & Component Libraries ?

Aucune expérience préalable n'est requise. Design Systems & Component Libraries sur CoddyKit est structuré pour les débutants jusqu'aux apprenants avancés, donc tu peux commencer ici ou depuis le début et avancer à ton rythme. Ceci est la leçon 2 sur 4.

Combien de temps prend la leçon « Props, état et gestion des événements » ?

La plupart des leçons CoddyKit prennent environ 5–10 minutes. Chacune est courte et interactive, tu progresses régulièrement et tu repiques exactement où tu t'es arrêté sur le web et l'app.

Peux-tu écrire et exécuter du code dans cette leçon Design Systems & Component Libraries ?

Oui. Chaque leçon Design Systems & Component Libraries inclut un éditeur de code intégré, tu écris et exécutes du vrai code directement dans ton navigateur et tu reçois des retours IA instantanés — aucune configuration locale requise.

Toutes les leçons de ce cours

← Retour à Design Systems & Component Libraries